[Kernel-packages] [Bug 1881699] Re: No analog output
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (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/1881699 Title: No analog output Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After a fresh boot and login, there is no analog output. Only HDMI and bluetooth are available. It becomes available when I kill pulseaudio with 'pulseaudio -k' but the sound indicator only shows 'dummy' output and I cannot control the output from the sound settings or the sound indicator. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu36 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: j-lallement 184080 F pulseaudio /dev/snd/controlC1: j-lallement 184080 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jun 2 06:32:09 2020 InstallationDate: Installed on 2020-05-31 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/21/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: FNCML357.0032.2019.1021.1624 dmi.board.asset.tag: Default string dmi.board.name: NUC10i7FNB dmi.board.vendor: Intel Corporation dmi.board.version: K61360-302 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrFNCML357.0032.2019.1021.1624:bd10/21/2019:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrK61081-302:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: FN dmi.product.name: NUC10i7FNH dmi.product.sku: BXNUC10i7FNH dmi.product.version: K61081-302 dmi.sys.vendor: Intel(R) Client Systems --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu36 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: j-lallement 3669 F pulseaudio /dev/snd/controlC0: j-lallement 3669 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-05-31 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527) MachineType: Intel(R) Client Systems NUC10i7FNH NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: pulseaudio 1:13.99.1-1ubuntu3 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_huyn9u@/vmlinuz-5.4.0-26-generic root=ZFS=rpool/ROOT/ubuntu_huyn9u ro snd-intel-dspcfg.dsp_driver=1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 Tags: groovy Uname: Linux 5.4.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/21/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: FNCML357.0032.2019.1021.1624 dmi.board.asset.tag: Default string dmi.board.name: NUC10i7FNB dmi.board.vendor: Intel Corporation dmi.board.version: K61360-302 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrFNCML357.0032.2019.1021.1624:bd10/21/2019:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrK61081-302:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: FN dmi.product.name: NUC10i7FNH dmi.product.sku: BXNUC10i7FNH dmi.product.version: K61081-302 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881699/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883598] Re: efi: Restrict efivar_ssdt_load when the kernel is locked down
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883598 Title: efi: Restrict efivar_ssdt_load when the kernel is locked down Status in linux package in Ubuntu: Confirmed Bug description: Upstream git commit 1957a85b0032 needs to be backported to older releases: efi: Restrict efivar_ssdt_load when the kernel is locked down efivar_ssdt_load allows the kernel to import arbitrary ACPI code from an EFI variable, which gives arbitrary code execution in ring 0. Prevent that when the kernel is locked down. Code introduced in 475fb4e8b2fd1d7b406ff3a7d21bc89a1e6f break-fix: 475fb4e8b2fd1d7b406ff3a7d21bc89a1e6f 1957a85b0032a81e6482ca4aab883643b8dae06e To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883598/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883229] Re: Ubuntu server installation on S3260M4 server gets failed
Hi Jeff the 18.04 worked fine ,so we are facing issue of UEFI+20.04 only on 20.04 on this server S3260 M4. Let me know is this workaround recommended of below steps/ Usually whenever a OS is installed in UEFI mode, after the OS install, boot loader will automatically create a boot entry mapping to /efi/boot/bootx64.efi. But for some reason, we are not able to boot Ubuntu 20.04 with the above boot entry. So, we went ahead and created a manual boot entry mapping to /efi/ubuntu/grub64.efi and this time we are able to successfully boot the OS. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883229 Title: Ubuntu server installation on S3260M4 server gets failed Status in grub2 package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Details/Description: - Ubuntu 20.04 fails on S3260 M4 with Gonga Beach in UEFI mode. Os get installed. However, upon rebooting OS never came up. Grub loads only to get hanged in a black screen. No options work later. Unable to collect Installer logs. How to reproduce: -- 1.Update S3260M4 M4 to bios build ucs-s3260-huu-4.1.2S36 2.Deploy Ubuntu 20.04 on S3260 M4. 3.Observe the installation proceeding and after installation OS reboots and loads the kernel and gets hanged on the black screen 4. The same OS works in Legacy mode in C3000 RAID controller card of LSI. Expected behavior: - Ubuntu 20.04 should get deployed in GB/DD-Raid in UEFI mode Screenshots -- Screenshot attached. Please let us know how to collect logs on this scenario Note :With MASS deployment we are able to deploy OS successfully with USFI method. Attached the logs of MASS server in this bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1883229/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883662] [NEW] After installing Ubuntu on my laptop the Touchpad has worked for a minute and then stopped.
Public bug reported: 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=0003 Version= N: Name="Sleep Button" P: Phys=PNP0C0E/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=4000 0 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=ab41 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input3 U: Uniq= H: Handlers=sysrq kbd event3 leds B: PROP=0 B: EV=120013 B: KEY=1 c0200 0 0 700f0203 3802078f870f401 febfffdfffef 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:00/input/input4 U: Uniq= H: Handlers=kbd event4 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus=0003 Vendor=046d Product=c05a Version=0111 N: Name="Logitech USB Optical Mouse" P: Phys=usb-:00:14.0-2/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-2/1-2:1.0/0003:046D:C05A.0001/input/input5 U: Uniq= H: Handlers=mouse0 event5 B: PROP=0 B: EV=17 B: KEY=7 0 0 0 0 B: REL=103 B: MSC=10 I: Bus=0019 Vendor= Product= Version= N: Name="Intel Virtual Button driver" P: Phys= S: Sysfs=/devices/pci:00/:00:1f.0/PNP0C09:00/INT33D6:00/input/input6 U: Uniq= H: Handlers=kbd event6 B: PROP=0 B: EV=13 B: KEY=1 0 1c 0 B: MSC=10 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Front Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1b.0/sound/card0/input7 U: Uniq= H: Handlers=event7 B: PROP=0 B: EV=21 B: SW=4 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:1b.0/sound/card0/input8 U: Uniq= H: Handlers=event8 B: PROP=0 B: EV=21 B: SW=140 I: Bus=0003 Vendor=2386 Product=0401 Version=0110 N: Name="Raydium Corporation Raydium Touch System" P: Phys=usb-:00:14.0-4/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-4/1-4:1.0/0003:2386:0401.0002/input/input12 U: Uniq= H: Handlers=mouse1 event9 B: PROP=2 B: EV=1b B: KEY=400 0 0 0 0 0 B: ABS=2608003 B: MSC=20 I: Bus=0019 Vendor= Product= Version= N: Name="Acer WMI hotkeys" P: Phys=wmi/input0 S: Sysfs=/devices/virtual/input/input19 U: Uniq= H: Handlers=rfkill kbd event10 B: PROP=0 B: EV=13 B: KEY=1c 0 0 0 0 160080c00 30 0 0 B: MSC=10 I: Bus=0003 Vendor=0bda Product=57cc Version=0004 N: Name="HD WebCam: HD WebCam" P: Phys=usb-:00:14.0-3/button S: Sysfs=/devices/pci:00/:00:14.0/usb1/1-3/1-3:1.0/input/input20 U: Uniq= H: Handlers=kbd event11 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 // my ubuntu versio: Distributor ID: Ubuntu Description:Ubuntu 18.04 LTS Release:18.04 Codename: bionic ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: LXDE Date: Tue Jun 16 08:28:05 2020 InstallationDate: Installed on 2020-06-15 (0 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1883662 Title: After installing Ubuntu on my laptop the Touchpad has worked for a minute and then stopped. Status in linux-signed package in Ubuntu: New 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=0003 Version= N: Name="Sleep Button" P: Phys=PNP0C0E/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0E:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=4000 0 0 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=LNXPWRBN/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXPWR
[Kernel-packages] [Bug 1878351] Re: System shutdown directly by pressing power button and releasing immediately on Dell Vostro 5301
@Kai, ideally the kernel fix would resolve the issue, unsure which userspace workqround is better -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878351 Title: System shutdown directly by pressing power button and releasing immediately on Dell Vostro 5301 Status in OEM Priority Project: Incomplete Status in gnome-session package in Ubuntu: Triaged Status in linux package in Ubuntu: Confirmed Bug description: kchsieh@kchsieh-laptop:~$ lsb_release -rd Description: Ubuntu 20.04 LTS (fossa-bulbasaur X23) Release: 20.04 kchsieh@kchsieh-laptop:~$ apt-cache policy systemd systemd: Installed: 245.4-4ubuntu3 Candidate: 245.4-4ubuntu3 Version table: *** 245.4-4ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status Expect: When press the button, the endSeesionDialog should show up. Actual: The system shutdown directly. When the issue happend: endSessionDialog is not triggered immediately after the first power button event, but triggered after the second power button event. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X23 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-10 (3 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. Vostro 5301 Package: systemd 245.4-4ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1010-oem root=UUID=b16fea1e-d8bc-4c71-a2e6-c43d269b40de ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1010.10-oem 5.6.8 Tags: focal Uname: Linux 5.6.0-1010-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/30/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.1.12 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.1.12:bd04/30/2020:svnDellInc.:pnVostro5301:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 5301 dmi.product.sku: 09FC dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1878351/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882659] [NEW] Night Light schedule on Dual Screens does not turn off on primary screen
You have been subscribed to a public bug: I have a dual monitor setup - primary screen is the internal display (laptop), secondary screen is an external monitor connected via VGA out. I have been using Night Light screen tinting since 19.10. The schedule is set to Sunset to Sunrise. it turns on as expected. When it turns off in the morning, it only turns off on the external monitor, the internal monitor still has the tint applied. I have to go into display settings and manually turn off and turn night light in order to revert the tint. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jun 9 12:43:35 2020 DistUpgraded: 2020-05-10 03:10:56,432 DEBUG icon theme changed, re-reading DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.6, 5.4.0-31-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-33-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Skylake GT2 [HD Graphics 520] [1043:10de] Subsystem: ASUSTeK Computer Inc. GM108M [GeForce 930MX] [1043:10de] InstallationDate: Installed on 2019-04-20 (416 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: ASUSTeK COMPUTER INC. X556UR ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-09 (30 days ago) dmi.bios.date: 10/24/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X556UR.309 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X556UR 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.:bvrX556UR.309:bd10/24/2016:svnASUSTeKCOMPUTERINC.:pnX556UR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX556UR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X556UR dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: gnome-settings-daemon Importance: Unknown Status: Unknown ** Affects: linux (Ubuntu) Importance: Low Status: Fix Released ** Tags: amd64 apport-bug focal ubuntu wayland-session -- Night Light schedule on Dual Screens does not turn off on primary screen https://bugs.launchpad.net/bugs/1882659 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878351] Re: System shutdown directly by pressing power button and releasing immediately on Dell Vostro 5301
@Sebastien I doubt that kernel fix can really solve the problem. If a use press the power button twice very quickly, it perhaps to run into the same problem. I think we still have to debounce or adjust the original commit of https://bugzilla.gnome.org/show_bug.cgi?id=688076. Recently, a lot of device implement fingerprints on power button, I am not sure if my assumption will happen on those hardwares, however, it is just my assumption, can be discussed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878351 Title: System shutdown directly by pressing power button and releasing immediately on Dell Vostro 5301 Status in OEM Priority Project: Incomplete Status in gnome-session package in Ubuntu: Triaged Status in linux package in Ubuntu: Confirmed Bug description: kchsieh@kchsieh-laptop:~$ lsb_release -rd Description: Ubuntu 20.04 LTS (fossa-bulbasaur X23) Release: 20.04 kchsieh@kchsieh-laptop:~$ apt-cache policy systemd systemd: Installed: 245.4-4ubuntu3 Candidate: 245.4-4ubuntu3 Version table: *** 245.4-4ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status Expect: When press the button, the endSeesionDialog should show up. Actual: The system shutdown directly. When the issue happend: endSessionDialog is not triggered immediately after the first power button event, but triggered after the second power button event. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X23 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-10 (3 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. Vostro 5301 Package: systemd 245.4-4ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1010-oem root=UUID=b16fea1e-d8bc-4c71-a2e6-c43d269b40de ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1010.10-oem 5.6.8 Tags: focal Uname: Linux 5.6.0-1010-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/30/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.1.12 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.1.12:bd04/30/2020:svnDellInc.:pnVostro5301:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 5301 dmi.product.sku: 09FC dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1878351/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882659] Re: Night Light schedule on Dual Screens does not turn off on primary screen
I'm quite surprised and still skeptical as to whether it was resolved in some other package. But the kernel you say fixed it is in official updates now so that's good enough for me. ** Package changed: gnome-settings-daemon (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Triaged => Fix Released ** No longer affects: gnome-settings-daemon -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882659 Title: Night Light schedule on Dual Screens does not turn off on primary screen Status in linux package in Ubuntu: Fix Released Bug description: I have a dual monitor setup - primary screen is the internal display (laptop), secondary screen is an external monitor connected via VGA out. I have been using Night Light screen tinting since 19.10. The schedule is set to Sunset to Sunrise. it turns on as expected. When it turns off in the morning, it only turns off on the external monitor, the internal monitor still has the tint applied. I have to go into display settings and manually turn off and turn night light in order to revert the tint. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jun 9 12:43:35 2020 DistUpgraded: 2020-05-10 03:10:56,432 DEBUG icon theme changed, re-reading DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.6, 5.4.0-31-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-33-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Skylake GT2 [HD Graphics 520] [1043:10de] Subsystem: ASUSTeK Computer Inc. GM108M [GeForce 930MX] [1043:10de] InstallationDate: Installed on 2019-04-20 (416 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: ASUSTeK COMPUTER INC. X556UR ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-09 (30 days ago) dmi.bios.date: 10/24/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X556UR.309 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X556UR 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.:bvrX556UR.309:bd10/24/2016:svnASUSTeKCOMPUTERINC.:pnX556UR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX556UR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X556UR dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882659/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883498] Re: Frequent Panic in ip6_expire_frag_queue->icmpv6_send on 4.4.0-184-generic
We are having the same bug (I believe) after upgrading from kernel linux-image-4.4.0-178-generic to linux-image-4.4.0-184-generic. We have around 100 VMs there are affected. For now, we have rolled back to the previous kernel. I am not sure why but not all VMs are affected, from what I have found, it looks like unbound (DNS server) is triggering the kernel oops our clients environment. I can help test a new kernel if that could help/be useful. I also have a kernel dump from linux-crashdump, but I am not currently sure if I am allow to share it, but I will try to figure it out if needed. ### Our kernel crash [ 128.503474] BUG: unable to handle kernel NULL pointer dereference at 0018 [ 128.503608] IP: [] icmp6_send+0x1fb/0x970 [ 128.503673] PGD 8004275f2067 PUD 427495067 PMD 0 [ 128.503736] Oops: [#1] SMP [ 128.503800] Modules linked in: vmw_vsock_vmci_transport vsock zfs(PO) zunicode(PO) zcommon(PO) znvpair(PO) spl(O) zavl(PO) vmw_balloon input_leds joydev serio_raw shpchp vmw_vmci i2c_piix4 mac_hid ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4 btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd vmwgfx ttm drm_kms_helper psmouse syscopyarea sysfillrect vmxnet3 sysimgblt vmw_pvscsi fb_sys_fops pata_acpi drm ahci libahci fjes [ 128.504798] CPU: 0 PID: 0 Comm: swapper/0 Tainted: P O 4.4.0-184-generic #214-Ubuntu [ 128.504990] Hardware name: VMware, Inc. VMware Virtual Platform/440BX Desktop Reference Platform, BIOS 6.00 12/12/2018 [ 128.505401] task: 81e13500 ti: 81e0 task.ti: 81e0 [ 128.505637] RIP: 0010:[] [] icmp6_send+0x1fb/0x970 [ 128.505892] RSP: 0018:88042d603d00 EFLAGS: 00010246 [ 128.506143] RAX: RBX: 880423804a00 RCX: 0020 [ 128.506409] RDX: 0001 RSI: 0200 RDI: 880427ce1856 [ 128.506686] RBP: 88042d603e20 R08: R09: 880427ce1866 [ 128.506962] R10: 0080 R11: R12: 880427ce184e [ 128.507246] R13: 81efb6c0 R14: 0001 R15: 0003 [ 128.507539] FS: () GS:88042d60() knlGS: [ 128.507842] CS: 0010 DS: ES: CR0: 80050033 [ 128.508176] CR2: 0018 CR3: 000427782000 CR4: 00360670 [ 128.508530] Stack: [ 128.508859] 0001 4a7e338b0c959fd7 [ 128.509212] 88042b139a38 88042b139a80 2b139a20 880427ce1856 [ 128.509577] 88040001 880427ce1866 [ 128.509945] Call Trace: [ 128.510314] [ 128.510324] [] ? _raw_spin_unlock_bh+0x20/0x50 [ 128.511089] [] icmpv6_send+0x21/0x30 [ 128.511483] [] ip6_expire_frag_queue+0x115/0x1b0 [ 128.511892] [] ? ip6_expire_frag_queue+0x1b0/0x1b0 [ 128.512301] [] ip6_frag_expire+0x1f/0x30 [ 128.512723] [] call_timer_fn+0x37/0x140 [ 128.513116] [] ? ip6_expire_frag_queue+0x1b0/0x1b0 [ 128.513509] [] run_timer_softirq+0x234/0x330 [ 128.513902] [] __do_softirq+0x109/0x2b0 [ 128.514291] [] irq_exit+0xa5/0xb0 [ 128.514673] [] smp_apic_timer_interrupt+0x50/0x70 [ 128.515045] [] apic_timer_interrupt+0xd4/0xe0 [ 128.515414] [ 128.515423] [] ? speculation_ctrl_update_tif+0x80/0x80 [ 128.516123] [] ? native_safe_halt+0x12/0x20 [ 128.516466] [] default_idle+0x1e/0xe0 [ 128.516802] [] arch_cpu_idle+0x15/0x20 [ 128.517124] [] default_idle_call+0x2a/0x40 [ 128.517441] [] cpu_startup_entry+0x303/0x360 [ 128.517757] [] rest_init+0x7c/0x80 [ 128.518055] [] start_kernel+0x483/0x4a4 [ 128.518367] [] ? early_idt_handler_array+0x120/0x120 [ 128.518665] [] x86_64_start_reservations+0x2a/0x2c [ 128.518952] [] x86_64_start_kernel+0x14a/0x16d [ 128.519234] Code: 8b 5c 24 40 75 46 f6 c2 02 74 05 f6 c2 30 75 3c 48 8b 43 58 44 89 5c 24 34 89 54 24 40 44 89 44 24 48 4c 89 4c 24 60 48 83 e0 fe <48> 8b 78 18 e8 4c 0b 03 00 41 89 c2 4c 8b 4c 24 60 44 8b 44 24 [ 128.520205] RIP [] icmp6_send+0x1fb/0x970 [ 128.520511] RSP [ 128.520818] CR2: 0018 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883498 Title: Frequent Panic in ip6_expire_frag_queue->icmpv6_send on 4.4.0-184-generic Status in linux package in Ubuntu: Confirmed Bug description: I happened to do an upgrade on a number of servers last week. Some of them got 4.4.0-179-generic and the ones upgraded a bit later during the week got 4.4.0-184-generic as it was just released. The ones with 4.4.0-184-generic started getting stuck. With linux-crashdump installe
[Kernel-packages] [Bug 1856387] Re: Freezing on boot since kernel 4.15.0-72-generic release
** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1856387 Title: Freezing on boot since kernel 4.15.0-72-generic release Status in linux package in Ubuntu: Invalid Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in linux-oem source package in Bionic: In Progress Bug description: After the update to install kernel 4.15.0-72-generic (a bit over a week ago) my computer will not boot. On boot, all I see is the purple screen with: Loading Linux 4.15.0-72-generic ... Loading initial ramdisk ... and nothing happens. Just sits there. I've waited about 5-10 minutes on occasion but to no avail. I've checked a number of logs in /var/log but not found anything. If I go into the advanced options and select kernel 4.15.0-70-generic, the computer boots normally. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-72-generic 4.15.0-72.81 ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tony 1977 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 14 21:53:14 2019 HibernationDevice: RESUME=UUID=5475ce25-e091-45e2-9811-9b5cddc08dd1 InstallationDate: Installed on 2018-09-16 (454 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Bus 001 Device 002: ID 046d:c063 Logitech, Inc. DELL Laser Mouse Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GIGABYTE Sabre 17WV8 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-70-generic root=UUID=9455257c-d3b7-4d61-853d-ab0b0ee40013 ro acpi=off RelatedPackageVersions: linux-restricted-modules-4.15.0-70-generic N/A linux-backports-modules-4.15.0-70-generic N/A linux-firmware 1.173.13 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/22/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F05 dmi.board.asset.tag: Tag 12345 dmi.board.name: Sabre 17WV8 dmi.board.vendor: GIGABYTE dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: GIGABYTE dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF05:bd05/22/2018:svnGIGABYTE:pnSabre17WV8:pvrNotApplicable:rvnGIGABYTE:rnSabre17WV8:rvrNotApplicable:cvnGIGABYTE:ct10:cvrN/A: dmi.product.family: Sabre dmi.product.name: Sabre 17WV8 dmi.product.version: Not Applicable dmi.sys.vendor: GIGABYTE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856387/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878351] Re: System shutdown directly by pressing power button and releasing immediately on Dell Vostro 5301
A debounce delay just doesn't sound right. If a user press the power button twice and the kernel dutifully reports two events, why a debounce is required when there are _actual_ two events? If there's a race between gsd and gnome-session, proper ordering should be imposed, instead of adding a delay to workaround the race. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878351 Title: System shutdown directly by pressing power button and releasing immediately on Dell Vostro 5301 Status in OEM Priority Project: Incomplete Status in gnome-session package in Ubuntu: Triaged Status in linux package in Ubuntu: Confirmed Bug description: kchsieh@kchsieh-laptop:~$ lsb_release -rd Description: Ubuntu 20.04 LTS (fossa-bulbasaur X23) Release: 20.04 kchsieh@kchsieh-laptop:~$ apt-cache policy systemd systemd: Installed: 245.4-4ubuntu3 Candidate: 245.4-4ubuntu3 Version table: *** 245.4-4ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status Expect: When press the button, the endSeesionDialog should show up. Actual: The system shutdown directly. When the issue happend: endSessionDialog is not triggered immediately after the first power button event, but triggered after the second power button event. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X23 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-10 (3 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. Vostro 5301 Package: systemd 245.4-4ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1010-oem root=UUID=b16fea1e-d8bc-4c71-a2e6-c43d269b40de ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1010.10-oem 5.6.8 Tags: focal Uname: Linux 5.6.0-1010-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/30/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.1.12 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.1.12:bd04/30/2020:svnDellInc.:pnVostro5301:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 5301 dmi.product.sku: 09FC dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1878351/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845860] Re: test_maps in ubuntu_bpf failed to build on B-hwe-edge 5.3 (BTF is required, but is missing or corrupted.)
** Tags added: sru-20200608 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1845860 Title: test_maps in ubuntu_bpf failed to build on B-hwe-edge 5.3 (BTF is required, but is missing or corrupted.) Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Eoan: Incomplete Status in linux source package in Focal: Incomplete Bug description: Issue found on 5.3 Bionic hwe: Running './test_maps' libbpf: BTF is required, but is missing or corrupted. Failed to load SK_SKB verdict prog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1845860/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882930] Re: focal/linux-raspi: Upstream raspberrypi patchset 2020-06-10
** Changed in: linux-raspi (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1882930 Title: focal/linux-raspi: Upstream raspberrypi patchset 2020-06-10 Status in linux-raspi package in Ubuntu: Invalid Status in linux-raspi source package in Focal: In Progress Bug description: Upstream raspberrypi patchset 2020-06-10 Ported from the following raspberrypi branch: rpi-5.4.y from https://github.com/raspberrypi/linux.git w1_therm: remove redundant assignments to variable ret w1_therm: Free the correct variable w1_therm: adding bulk read support to trigger multiple conversion on bus w1_therm: adding alarm sysfs entry w1_therm: optimizing temperature read timings w1_therm: adding eeprom sysfs entry w1_therm: adding resolution sysfs entry w1_therm: adding ext_power sysfs entry w1_therm: fix reset_select_slave during discovery w1_therm: adding code comments and code reordering overlays: Update upstream overlays after vc4-kms-v3d change overlays: i2c-gpio: Avoid open-drain warnings Revert "overlays: gpio-keys: Avoid open-drain warnings" snd_bcm2835: disable HDMI audio when vc4 is used (#3640) vc4: cec: Restore cec physical address on reconnect staging: vchiq_arm: Use g_dma_dev for dma_unmap_sg vc4: Set driver_name for card configs: Add SND_SOC_MAX98357A=m Add Micro Crystal RV-1805 to i2c-rtc overlays media: bcm2835-isp: fix bytes per line calculations for some image formats overlays: i2c-rtc-gpio: Fix trickle-resistor-ohms param net: rtl8192cu: fix gcc misleading whitespace warning overlays: Add spi0 overlay to support sc16is752 overlays: gpio-shutdown: Add information for Raspberry Pi 1 Model B rev 1 overlays: gpio-shutdown: Add information for SysV init / inittab overlays: i2c-rtc: Fix trickle-resistor-ohms param brcmfmac: BCM43436 needs dedicated firmware configs: Build HWMON core into kernel configs: Switch to upstream thermal sensor for RPi 4 - BCM2711_THERMAL ARM: dts: bcm2711-rpi: Remove downstream thermal sensor node Revert "thermal: brcmstb_thermal: Add BCM2838 support" Revert "thermal: brcmstb_thermal: Correct SoC name" ARM: configs: Build BCM2711 thermal as module ARM: dts: bcm2711: Enable thermal thermal: Add BCM2711 thermal driver dt-bindings: Add Broadcom AVS RO thermal media: bcm2835-unicam: change minimum number of vb2_queue buffers to 1 Revert "zswap: Uncross module parameter setting functions" ARM: dts: Update for new VCHIQ BCM2711 DMA support staging: vchiq_arm: Clean up 40-bit DMA support media: i2c: imx477: Return correct result on sensor id verification drm/vc4: Add FKMS as an acceptable node for dma ranges. drm/vc4: Adopt the dma configuration from the HVS or V3D component configs: Add ZSWAP=y, ZBUD=m, Z3FOLD=m zswap: Defer zswap initialisation zswap: Uncross module parameter setting functions media: bcm2835-unicam: Retain packing information on G_FMT Switch to snd_soc_dai_set_bclk_ratio overlays: Fix audio parameter of vc4-kms-v3d configs: Restore missing NF_TABLES settings staging:vc04_services: bcm2835-camera: Request headers with I-frame staging:vc04_services: bcm2835-codec: Avoid fragmenting buffers staging:vc04_services: bcm2835-codec: Request headers with I-frame staging: vc04_services: mmal-vchiq: Update parameters list drm/vc4: Fix VIC usage with Broadcast RGB sc16is7xx: Fix for hardware flow control media: bcm2835-unicam: Always service interrupts configs: Use the upstream cpufreq driver configs: Include the firmware-clocks driver ARM: dts: Enable firmware-clocks on all Pis defconfig: Add CMA and system dma-heaps to the config dma-heap: Make the symbol 'dma_heap_ioctl_cmds' static dma-buf: fix resource leak on -ENOTTY error return path dma-buf: heaps: Remove redundant heap identifier from system heap name dma-buf: heaps: Use _IOCTL_ for userspace IOCTL identifier kselftests: Add dma-heap test dma-buf: heaps: Add CMA heap to dmabuf heaps dma-buf: heaps: Add system heap to dmabuf heaps dma-buf: heaps: Add heap helpers dma-buf: Add dma-buf heaps framework udmabuf: fix dma-buf cpu access udmabuf: implement begin_cpu_access/end_cpu_access hooks udmabuf: separate out creating/destroying scatter-table udmabuf: add a pointer to the miscdevice in dma-buf private data udmabuf: use cache_sgt_mapping option udmabuf: Remove deleted map/unmap handlers. configs: Add imx477 sensor driver to all Raspberry Pi defconfigs media: i2c: imx477: Add support for adaptive frame control media: i2c: Add driver for Sony IMX477 sensor dtoverlays: Add IMX477 sensor overlay dt-bindings: media: i2c: Add IMX477 CMOS sensor binding raspberrypi: dts: Switch to discrete ALSA devices overlays: Move "fixed-clock" nodes to the root overlays: tc358743: Use intra-overlay fragm
[Kernel-packages] [Bug 1878351] Re: System shutdown directly by pressing power button and releasing immediately on Dell Vostro 5301
if gnome-session handle those two events, then it goes to prepare_shutdown which is current result. If the original implementation of https://bugzilla.gnome.org/show_bug.cgi?id=688076 is correct, then it is expected result, and we accept it. Unless the commit of https://bugzilla.gnome.org/show_bug.cgi?id=688076 have to tweak to adjust two quick button press. A debounce is mentioned by the maintainer, not what my original thought, my thought original implement need to do some adjust for handling such corner case. https://gitlab.gnome.org/GNOME/gnome-session/-/merge_requests/46#note_836061 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878351 Title: System shutdown directly by pressing power button and releasing immediately on Dell Vostro 5301 Status in OEM Priority Project: Incomplete Status in gnome-session package in Ubuntu: Triaged Status in linux package in Ubuntu: Confirmed Bug description: kchsieh@kchsieh-laptop:~$ lsb_release -rd Description: Ubuntu 20.04 LTS (fossa-bulbasaur X23) Release: 20.04 kchsieh@kchsieh-laptop:~$ apt-cache policy systemd systemd: Installed: 245.4-4ubuntu3 Candidate: 245.4-4ubuntu3 Version table: *** 245.4-4ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status Expect: When press the button, the endSeesionDialog should show up. Actual: The system shutdown directly. When the issue happend: endSessionDialog is not triggered immediately after the first power button event, but triggered after the second power button event. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X23 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-10 (3 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. Vostro 5301 Package: systemd 245.4-4ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1010-oem root=UUID=b16fea1e-d8bc-4c71-a2e6-c43d269b40de ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1010.10-oem 5.6.8 Tags: focal Uname: Linux 5.6.0-1010-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/30/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.1.12 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.1.12:bd04/30/2020:svnDellInc.:pnVostro5301:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 5301 dmi.product.sku: 09FC dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1878351/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878351] Re: System shutdown directly by pressing power button and releasing immediately on Dell Vostro 5301
gnome-session did handle those two events, and it goes to prepare_shutdown which is current result. If the original implementation of https://bugzilla.gnome.org/show_bug.cgi?id=688076 is correct, then it is expected result, and we accept it. Unless the commit of https://bugzilla.gnome.org/show_bug.cgi?id=688076 need to be tweaked to adjust two quick button press. A debounce is mentioned by the maintainer, not what my first implementation, I thought original implemention need to do some adjustment for handling the case. You can check the maintainer's comment. https://gitlab.gnome.org/GNOME/gnome-session/-/merge_requests/46#note_836061 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878351 Title: System shutdown directly by pressing power button and releasing immediately on Dell Vostro 5301 Status in OEM Priority Project: Incomplete Status in gnome-session package in Ubuntu: Triaged Status in linux package in Ubuntu: Confirmed Bug description: kchsieh@kchsieh-laptop:~$ lsb_release -rd Description: Ubuntu 20.04 LTS (fossa-bulbasaur X23) Release: 20.04 kchsieh@kchsieh-laptop:~$ apt-cache policy systemd systemd: Installed: 245.4-4ubuntu3 Candidate: 245.4-4ubuntu3 Version table: *** 245.4-4ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status Expect: When press the button, the endSeesionDialog should show up. Actual: The system shutdown directly. When the issue happend: endSessionDialog is not triggered immediately after the first power button event, but triggered after the second power button event. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X23 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-10 (3 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. Vostro 5301 Package: systemd 245.4-4ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1010-oem root=UUID=b16fea1e-d8bc-4c71-a2e6-c43d269b40de ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1010.10-oem 5.6.8 Tags: focal Uname: Linux 5.6.0-1010-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/30/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.1.12 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.1.12:bd04/30/2020:svnDellInc.:pnVostro5301:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 5301 dmi.product.sku: 09FC dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1878351/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883670] [NEW] Disable IEC958 on HP Thunderbolt Dock
Public bug reported: [Impact] On HP Thunderbolt Dock, unusable SPDIF can be selected as output from PulseAudio. [Fix] Disable IEC958 (SPDIF) through ALSA UCM. [Test] With the UCM applied, `pactl` and audio panel in gnome-control-center no longer have SPDIF option. [Regression Potential] Low. This fix limits to the HP Thunderbolt Dock, other devices are unaffected. ** Affects: alsa-lib (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1883670 Title: Disable IEC958 on HP Thunderbolt Dock Status in alsa-lib package in Ubuntu: New Bug description: [Impact] On HP Thunderbolt Dock, unusable SPDIF can be selected as output from PulseAudio. [Fix] Disable IEC958 (SPDIF) through ALSA UCM. [Test] With the UCM applied, `pactl` and audio panel in gnome-control-center no longer have SPDIF option. [Regression Potential] Low. This fix limits to the HP Thunderbolt Dock, other devices are unaffected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1883670/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883676] [NEW] ZFS performance drops suddenly
Public bug reported:
Run Phoronix Flexible IO / Random write benchmark.
After running the benchmark repeatedly multiple times (occasionally it can be
30 minutes or 8 hours), the performance drops suddenly. The only way (I know
of) to get back to high performance is reboot.
---
$ for i in $(seq 1 1000); do printf "2\n4\n2\n1\n1\n1\nn\n" |
phoronix-test-suite run fio | awk '/Average.*IOPS/ {print $2}' >> /tmp/iops;
done
$ less /tmp/iops
...
2095
2095
2093
783
388
389
...
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: zfsutils-linux 0.7.5-1ubuntu16.9
ProcVersionSignature: User Name 5.3.0-1023.25~18.04.1-aws 5.3.18
Uname: Linux 5.3.0-1023-aws x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7.15
Architecture: amd64
Date: Tue Jun 16 08:55:01 2020
Ec2AMI: ami-06fd83ae47b05282f
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: us-east-1f
Ec2InstanceType: c4.xlarge
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
SourcePackage: zfs-linux
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.sudoers.d.zfs: [deleted]
** Affects: zfs-linux (Ubuntu)
Importance: Undecided
Status: Confirmed
** Tags: amd64 apport-bug bionic ec2-images
--
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/1883676
Title:
ZFS performance drops suddenly
Status in zfs-linux package in Ubuntu:
Confirmed
Bug description:
Run Phoronix Flexible IO / Random write benchmark.
After running the benchmark repeatedly multiple times (occasionally it can be
30 minutes or 8 hours), the performance drops suddenly. The only way (I know
of) to get back to high performance is reboot.
---
$ for i in $(seq 1 1000); do printf "2\n4\n2\n1\n1\n1\nn\n" |
phoronix-test-suite run fio | awk '/Average.*IOPS/ {print $2}' >> /tmp/iops;
done
$ less /tmp/iops
...
2095
2095
2093
783
388
389
...
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: zfsutils-linux 0.7.5-1ubuntu16.9
ProcVersionSignature: User Name 5.3.0-1023.25~18.04.1-aws 5.3.18
Uname: Linux 5.3.0-1023-aws x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7.15
Architecture: amd64
Date: Tue Jun 16 08:55:01 2020
Ec2AMI: ami-06fd83ae47b05282f
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: us-east-1f
Ec2InstanceType: c4.xlarge
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
SourcePackage: zfs-linux
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.sudoers.d.zfs: [deleted]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1883676/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883676] Re: ZFS performance drops suddenly
Reproducible.
** Changed in: zfs-linux (Ubuntu)
Status: New => Confirmed
--
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/1883676
Title:
ZFS performance drops suddenly
Status in zfs-linux package in Ubuntu:
Confirmed
Bug description:
Run Phoronix Flexible IO / Random write benchmark.
After running the benchmark repeatedly multiple times (occasionally it can be
30 minutes or 8 hours), the performance drops suddenly. The only way (I know
of) to get back to high performance is reboot.
---
$ for i in $(seq 1 1000); do printf "2\n4\n2\n1\n1\n1\nn\n" |
phoronix-test-suite run fio | awk '/Average.*IOPS/ {print $2}' >> /tmp/iops;
done
$ less /tmp/iops
...
2095
2095
2093
783
388
389
...
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: zfsutils-linux 0.7.5-1ubuntu16.9
ProcVersionSignature: User Name 5.3.0-1023.25~18.04.1-aws 5.3.18
Uname: Linux 5.3.0-1023-aws x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7.15
Architecture: amd64
Date: Tue Jun 16 08:55:01 2020
Ec2AMI: ami-06fd83ae47b05282f
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: us-east-1f
Ec2InstanceType: c4.xlarge
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
SourcePackage: zfs-linux
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.sudoers.d.zfs: [deleted]
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1883676/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848921] Re: iwlwifi firmware crashes intel 9260ac [8086:2526] subsystem [8086:0010]
I don't seem to have this problem on Ubuntu 18.04, 5.4.0-37 hwe-edge kernel. I don't seem to have this problem on Ubuntu 20.04 live session either. At least. speedtest can't reproduce the issue. Even tried rebooting from Windows. Those who have the problem and dual boot, could you try upgrading your Windows driver to latest and see if it helps? I once had a RTL Ethernet card issue on Linux and it ended up getting fixed by upgrading driver on Windows. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848921 Title: iwlwifi firmware crashes intel 9260ac [8086:2526] subsystem [8086:0010] Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 19.10 Kernel 5.3.0-18-generic Hardware: Thinkpad T460p (also tested on T480s) with Intel 9260ac wifi card. Expected: Wifi connects, uploads/downloads as normal Symptom: Wifi connects, as soon as an upload/download (any heavy traffic) start, the system comes to a crawl, becomes barely usable, and I end up opening a prompt to reboot. The system is unusable. This happens even with the Live USB version. The only solution I found was to download a different (newer) firmware. Latest version from: https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi This is iwlwifi-9260-th-b0-jf-b0-34.618819.0.tgz I then manually copy the contained firmware to /lib/firmware, remove all other versions and make a link to iwlwifi-9260-th-b0-jf-46.ucode that the kernel expects to load. This completely resolves the issue. This is the carsh log (Thinkpad T460p, but identical to T480s, all fresh installs): Oct 20 01:51:13 weywot kernel: iwlwifi :03:00.0: Error sending SCAN_CFG_CMD: time out after 2000ms. Oct 20 01:51:13 weywot kernel: iwlwifi :03:00.0: Current CMD queue read_ptr 64 write_ptr 65 Oct 20 01:51:13 weywot kernel: iwlwifi :03:00.0: HW error, resetting before reading Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: Start IWL Error Log Dump: Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: Status: 0x0080, count: 609870115 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: Loaded firmware version: 46.6bf1df06.0 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x36BC8FCF | ADVANCED_SYSASSERT Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x28A5819E | trm_hw_status0 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x77944CFA | trm_hw_status1 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x018004F5 | branchlink2 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xEBCFC5F1 | interruptlink1 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x07206003 | interruptlink2 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xE956CDF4 | data1 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x7D692903 | data2 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xAD22F469 | data3 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x1040C00E | beacon time Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x0FF6877F | tsf low Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x82686A2F | tsf hi Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xB715D7B2 | time gp1 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x5EC31049 | time gp2 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xF7FD7FF6 | uCode revision type Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x31225172 | uCode version major Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xFD1DB8B4 | uCode version minor Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xC000F415 | hw version Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x7F9AFDD4 | board version Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xD5FD2F0F | hcmd Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x8F81D049 | isr0 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xEDDFDA7B | isr1 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xD9409AD7 | isr2 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x5AF7DA77 | isr3 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x400240BE | isr4 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xEEF6DF6B | last cmd Id Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x40528540 | wait_event Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xB9BBD6FD | l2p_control Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xC21B6142 | l2p_duration Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x7BDF6F9E | l2p_mhvalid Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x190AF41B | l2p_addr_match Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x7FF297FF | lmpm_pmg_sel Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x5248C715 | timestamp Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0:
[Kernel-packages] [Bug 1883681] [NEW] System freezes on specific kernel
You have been subscribed to a public bug: The servers will be running fine for some time and suddenly will freeze. It won't even respond to ping requests. We have to reboot the servers again to bring it back online but it won't be stable and will not respond again. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: crash kernel-bug -- System freezes on specific kernel https://bugs.launchpad.net/bugs/1883681 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882659] Re: Night Light schedule on Dual Screens does not turn off on primary screen
It was a regression though yes, I am not sure in which package. Previously it was working as intended. But I noticed the buggy behavior some time beginning of June and hence the initial bug report. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882659 Title: Night Light schedule on Dual Screens does not turn off on primary screen Status in linux package in Ubuntu: Fix Released Bug description: I have a dual monitor setup - primary screen is the internal display (laptop), secondary screen is an external monitor connected via VGA out. I have been using Night Light screen tinting since 19.10. The schedule is set to Sunset to Sunrise. it turns on as expected. When it turns off in the morning, it only turns off on the external monitor, the internal monitor still has the tint applied. I have to go into display settings and manually turn off and turn night light in order to revert the tint. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jun 9 12:43:35 2020 DistUpgraded: 2020-05-10 03:10:56,432 DEBUG icon theme changed, re-reading DistroCodename: focal DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.6, 5.4.0-31-generic, x86_64: installed virtualbox, 6.1.6, 5.4.0-33-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Skylake GT2 [HD Graphics 520] [1043:10de] Subsystem: ASUSTeK Computer Inc. GM108M [GeForce 930MX] [1043:10de] InstallationDate: Installed on 2019-04-20 (416 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: ASUSTeK COMPUTER INC. X556UR ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-09 (30 days ago) dmi.bios.date: 10/24/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X556UR.309 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X556UR 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.:bvrX556UR.309:bd10/24/2016:svnASUSTeKCOMPUTERINC.:pnX556UR:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX556UR:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X556UR dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882659/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883681] Re: System freezes on specific kernel
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883681 Title: System freezes on specific kernel Status in linux package in Ubuntu: New Bug description: The servers will be running fine for some time and suddenly will freeze. It won't even respond to ping requests. We have to reboot the servers again to bring it back online but it won't be stable and will not respond again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883681/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883681] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1883681 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883681 Title: System freezes on specific kernel Status in linux package in Ubuntu: Incomplete Bug description: The servers will be running fine for some time and suddenly will freeze. It won't even respond to ping requests. We have to reboot the servers again to bring it back online but it won't be stable and will not respond again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883681/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883670] Re: Disable IEC958 on HP Thunderbolt Dock
debdiff for Groovy ** Also affects: alsa-lib (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: alsa-lib (Ubuntu Focal) Importance: Undecided Status: New ** Patch added: "alsa-lib_1.2.2-2.3.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1883670/+attachment/5384334/+files/alsa-lib_1.2.2-2.3.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1883670 Title: Disable IEC958 on HP Thunderbolt Dock Status in HWE Next: New Status in alsa-lib package in Ubuntu: New Status in alsa-lib source package in Focal: New Status in alsa-lib source package in Groovy: New Bug description: [Impact] On HP Thunderbolt Dock, unusable SPDIF can be selected as output from PulseAudio. [Fix] Disable IEC958 (SPDIF) through ALSA UCM. [Test] With the UCM applied, `pactl` and audio panel in gnome-control-center no longer have SPDIF option. [Regression Potential] Low. This fix limits to the HP Thunderbolt Dock, other devices are unaffected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1883670/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883670] Re: Disable IEC958 on HP Thunderbolt Dock
debdiff for Focal ** Patch added: "alsa-lib_1.2.2-2.1ubuntu1.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1883670/+attachment/5384335/+files/alsa-lib_1.2.2-2.1ubuntu1.debdiff ** Tags added: oem-priority originate-from-1880102 stella -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1883670 Title: Disable IEC958 on HP Thunderbolt Dock Status in HWE Next: New Status in alsa-lib package in Ubuntu: New Status in alsa-lib source package in Focal: New Status in alsa-lib source package in Groovy: New Bug description: [Impact] On HP Thunderbolt Dock, unusable SPDIF can be selected as output from PulseAudio. [Fix] Disable IEC958 (SPDIF) through ALSA UCM. [Test] With the UCM applied, `pactl` and audio panel in gnome-control-center no longer have SPDIF option. [Regression Potential] Low. This fix limits to the HP Thunderbolt Dock, other devices are unaffected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1883670/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883498] Re: Frequent Panic in ip6_expire_frag_queue->icmpv6_send on 4.4.0-184-generic
We had the same behaviour like Dennis! Kernel Panic after aprox. 4 our on kernel 4.4.0-184 Unbound installed as well with version 1.5.8 Unfortunately i have no crashdump by hand, but our panic was "same" as Dennis with ipv6 messages. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883498 Title: Frequent Panic in ip6_expire_frag_queue->icmpv6_send on 4.4.0-184-generic Status in linux package in Ubuntu: Confirmed Bug description: I happened to do an upgrade on a number of servers last week. Some of them got 4.4.0-179-generic and the ones upgraded a bit later during the week got 4.4.0-184-generic as it was just released. The ones with 4.4.0-184-generic started getting stuck. With linux-crashdump installed I obtained the dmesgs and crash dumps. The backtrace appears somewhat similar to #202669 but that one only happened on bare hardware for us - this one is on KVM virtual instances. #202669 paniced in icmpv6_route_lookup and this one dies already in icmpv6_send. Between 2020-06-11 and 2020-06-15, on a set of 12 VMs running 4.4.0-184-generic, there were 85 crashes like this, on servers with noticeable IPv6 traffic. All of the 12 VMs with 4.4.0-184-generic crashed at least once. (There are more than 12 VMs experiencing this, this is just the set I had linux-crashdump on.) [57063.487084] BUG: unable to handle kernel NULL pointer dereference at 0018 [57063.487184] IP: [] icmp6_send+0x1fb/0x970 [57063.487218] PGD 0 [57063.487231] Oops: [#1] SMP [57063.488665] Call Trace: [57063.488679] [57063.488705] [] ? __netif_receive_skb+0x18/0x60 [57063.488739] [] ? task_tick_fair+0x4c8/0x8e0 [57063.488771] [] ? _raw_spin_unlock_bh+0x20/0x50 [57063.488802] [] icmpv6_send+0x21/0x30 [57063.488829] [] ip6_expire_frag_queue+0x115/0x1b0 [57063.488862] [] ? nf_ct_net_exit+0x50/0x50 [nf_defrag_ipv6] [57063.488897] [] nf_ct_frag6_expire+0x1f/0x30 [nf_defrag_ipv6] [57063.488937] [] call_timer_fn+0x37/0x140 [57063.488965] [] ? nf_ct_net_exit+0x50/0x50 [nf_defrag_ipv6] [57063.489002] [] run_timer_softirq+0x234/0x330 ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883498/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879973] Re: There is no sound from the built-in speakers and does not see the built-in microphone
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1879973 Title: There is no sound from the built-in speakers and does not see the built-in microphone Status in linux package in Ubuntu: Fix Released Bug description: After update my Inspiron 5490 from Ubuntu 18.04 to 20.04 system see only "Dummy Sound". I updated kernel to 5.6.13-050613-lowlatency, reinstall pulseaudio, add "options snd-hda-intel dmic_detect=0" to /etc/modprobe.d/alsa- base.con, add "blacklist snd_soc_skl" to /etc/modprobe.d/blacklist.conf. I applied the solution from this source: https://bugs.launchpad.net/ubuntu/+source/alsa- driver/+bug/1876238. I still have this problem. Audio: Device-1: Intel driver: sof-audio-pci Sound Server: ALSA v: k5.6.13-050613-lowlatency $ aplay -l List of PLAYBACK Hardware Devices card 0: sofhdadsp [sof-hda-dsp], device 0: HDA Analog (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 1: HDA Digital (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 3: HDMI1 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 4: HDMI2 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: sofhdadsp [sof-hda-dsp], device 5: HDMI3 (*) [] Subdevices: 1/1 Subdevice #0: subdevice #0 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: evince 3.36.0-2 Uname: Linux 5.6.13-050613-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 21 17:18:36 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00 InstallationDate: Installed on 2020-01-31 (111 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 SourcePackage: evince UpgradeStatus: Upgraded to focal on 2020-05-18 (2 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-31 (113 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) Tags: focal Uname: Linux 5.6.13-050613-lowlatency x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D5p', '/dev/snd/pcmC0D4p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D1c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1+X00 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-31 (113 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0bda:5538 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5490 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=4b1d1189-110f-4f43-a4ad-eaf0b866e9c4 ro mem_sleep_default=deep quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backport
[Kernel-packages] [Bug 1883681] Re: System freezes on specific kernel
apport information ** Tags added: apport-collected xenial ** Description changed: - The servers will be running fine for some time and suddenly will freeze. - It won't even respond to ping requests. We have to reboot the servers - again to bring it back online but it won't be stable and will not - respond again. + The servers will be running fine for some time and suddenly will freeze. It won't even respond to ping requests. We have to reboot the servers again to bring it back online but it won't be stable and will not respond again. + --- + AlsaDevices: + total 0 + crw-rw 1 root audio 116, 1 Jun 15 17:52 seq + crw-rw 1 root audio 116, 33 Jun 15 17:52 timer + AplayDevices: Error: [Errno 2] No such file or directory + ApportVersion: 2.20.1-0ubuntu2.23 + Architecture: amd64 + ArecordDevices: Error: [Errno 2] No such file or directory + AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: + DistroRelease: Ubuntu 16.04 + HibernationDevice: RESUME=UUID=fe587596-cd68-4bbf-ae67-0e501fd6159c + IwConfig: + lono wireless extensions. + + ens160no wireless extensions. + Lsusb: Error: command ['lsusb'] failed with exit code 1: + MachineType: VMware, Inc. VMware Virtual Platform + Package: linux (not installed) + PciMultimedia: + + ProcEnviron: + TERM=screen + PATH=(custom, no user) + LANG=en_US + SHELL=/bin/bash + ProcFB: 0 svgadrmfb + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-184-generic root=/dev/mapper/cdns01--vg-root ro crashkernel=384M-:128M + ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 + RelatedPackageVersions: + linux-restricted-modules-4.4.0-184-generic N/A + linux-backports-modules-4.4.0-184-generic N/A + linux-firmware 1.157.23 + RfKill: Error: [Errno 2] No such file or directory + Tags: xenial + Uname: Linux 4.4.0-184-generic x86_64 + UpgradeStatus: Upgraded to xenial on 2017-05-15 (1127 days ago) + UserGroups: + + _MarkForUpload: True + dmi.bios.date: 09/17/2015 + dmi.bios.vendor: Phoenix Technologies LTD + dmi.bios.version: 6.00 + dmi.board.name: 440BX Desktop Reference Platform + dmi.board.vendor: Intel Corporation + dmi.board.version: None + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 1 + dmi.chassis.vendor: No Enclosure + dmi.chassis.version: N/A + dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd09/17/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: + dmi.product.name: VMware Virtual Platform + dmi.product.version: None + dmi.sys.vendor: VMware, Inc. ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1883681/+attachment/5384337/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883681 Title: System freezes on specific kernel Status in linux package in Ubuntu: Incomplete Bug description: The servers will be running fine for some time and suddenly will freeze. It won't even respond to ping requests. We have to reboot the servers again to bring it back online but it won't be stable and will not respond again. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 15 17:52 seq crw-rw 1 root audio 116, 33 Jun 15 17:52 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=fe587596-cd68-4bbf-ae67-0e501fd6159c IwConfig: lono wireless extensions. ens160no wireless extensions. Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-184-generic root=/dev/mapper/cdns01--vg-root ro crashkernel=384M-:128M ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 RelatedPackageVersions: linux-restricted-modules-4.4.0-184-generic N/A linux-backports-modules-4.4.0-184-generic N/A linux-firmware 1.157.23 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-184-generic x86_64 UpgradeStatus: Upgraded to xenial on 2017-05-15 (1127 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 09/17/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi
[Kernel-packages] [Bug 1883681] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1883681/+attachment/5384339/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883681 Title: System freezes on specific kernel Status in linux package in Ubuntu: Incomplete Bug description: The servers will be running fine for some time and suddenly will freeze. It won't even respond to ping requests. We have to reboot the servers again to bring it back online but it won't be stable and will not respond again. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 15 17:52 seq crw-rw 1 root audio 116, 33 Jun 15 17:52 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=fe587596-cd68-4bbf-ae67-0e501fd6159c IwConfig: lono wireless extensions. ens160no wireless extensions. Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-184-generic root=/dev/mapper/cdns01--vg-root ro crashkernel=384M-:128M ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 RelatedPackageVersions: linux-restricted-modules-4.4.0-184-generic N/A linux-backports-modules-4.4.0-184-generic N/A linux-firmware 1.157.23 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-184-generic x86_64 UpgradeStatus: Upgraded to xenial on 2017-05-15 (1127 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 09/17/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd09/17/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883681/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883681] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1883681/+attachment/5384344/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883681 Title: System freezes on specific kernel Status in linux package in Ubuntu: Incomplete Bug description: The servers will be running fine for some time and suddenly will freeze. It won't even respond to ping requests. We have to reboot the servers again to bring it back online but it won't be stable and will not respond again. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 15 17:52 seq crw-rw 1 root audio 116, 33 Jun 15 17:52 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=fe587596-cd68-4bbf-ae67-0e501fd6159c IwConfig: lono wireless extensions. ens160no wireless extensions. Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-184-generic root=/dev/mapper/cdns01--vg-root ro crashkernel=384M-:128M ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 RelatedPackageVersions: linux-restricted-modules-4.4.0-184-generic N/A linux-backports-modules-4.4.0-184-generic N/A linux-firmware 1.157.23 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-184-generic x86_64 UpgradeStatus: Upgraded to xenial on 2017-05-15 (1127 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 09/17/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd09/17/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883681/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883681] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1883681/+attachment/5384343/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883681 Title: System freezes on specific kernel Status in linux package in Ubuntu: Incomplete Bug description: The servers will be running fine for some time and suddenly will freeze. It won't even respond to ping requests. We have to reboot the servers again to bring it back online but it won't be stable and will not respond again. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 15 17:52 seq crw-rw 1 root audio 116, 33 Jun 15 17:52 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=fe587596-cd68-4bbf-ae67-0e501fd6159c IwConfig: lono wireless extensions. ens160no wireless extensions. Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-184-generic root=/dev/mapper/cdns01--vg-root ro crashkernel=384M-:128M ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 RelatedPackageVersions: linux-restricted-modules-4.4.0-184-generic N/A linux-backports-modules-4.4.0-184-generic N/A linux-firmware 1.157.23 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-184-generic x86_64 UpgradeStatus: Upgraded to xenial on 2017-05-15 (1127 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 09/17/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd09/17/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883681/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883681] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1883681/+attachment/5384340/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883681 Title: System freezes on specific kernel Status in linux package in Ubuntu: Incomplete Bug description: The servers will be running fine for some time and suddenly will freeze. It won't even respond to ping requests. We have to reboot the servers again to bring it back online but it won't be stable and will not respond again. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 15 17:52 seq crw-rw 1 root audio 116, 33 Jun 15 17:52 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=fe587596-cd68-4bbf-ae67-0e501fd6159c IwConfig: lono wireless extensions. ens160no wireless extensions. Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-184-generic root=/dev/mapper/cdns01--vg-root ro crashkernel=384M-:128M ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 RelatedPackageVersions: linux-restricted-modules-4.4.0-184-generic N/A linux-backports-modules-4.4.0-184-generic N/A linux-firmware 1.157.23 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-184-generic x86_64 UpgradeStatus: Upgraded to xenial on 2017-05-15 (1127 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 09/17/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd09/17/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883681/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883681] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1883681/+attachment/5384342/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883681 Title: System freezes on specific kernel Status in linux package in Ubuntu: Incomplete Bug description: The servers will be running fine for some time and suddenly will freeze. It won't even respond to ping requests. We have to reboot the servers again to bring it back online but it won't be stable and will not respond again. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 15 17:52 seq crw-rw 1 root audio 116, 33 Jun 15 17:52 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=fe587596-cd68-4bbf-ae67-0e501fd6159c IwConfig: lono wireless extensions. ens160no wireless extensions. Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-184-generic root=/dev/mapper/cdns01--vg-root ro crashkernel=384M-:128M ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 RelatedPackageVersions: linux-restricted-modules-4.4.0-184-generic N/A linux-backports-modules-4.4.0-184-generic N/A linux-firmware 1.157.23 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-184-generic x86_64 UpgradeStatus: Upgraded to xenial on 2017-05-15 (1127 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 09/17/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd09/17/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883681/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883681] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1883681/+attachment/5384345/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883681 Title: System freezes on specific kernel Status in linux package in Ubuntu: Incomplete Bug description: The servers will be running fine for some time and suddenly will freeze. It won't even respond to ping requests. We have to reboot the servers again to bring it back online but it won't be stable and will not respond again. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 15 17:52 seq crw-rw 1 root audio 116, 33 Jun 15 17:52 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=fe587596-cd68-4bbf-ae67-0e501fd6159c IwConfig: lono wireless extensions. ens160no wireless extensions. Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-184-generic root=/dev/mapper/cdns01--vg-root ro crashkernel=384M-:128M ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 RelatedPackageVersions: linux-restricted-modules-4.4.0-184-generic N/A linux-backports-modules-4.4.0-184-generic N/A linux-firmware 1.157.23 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-184-generic x86_64 UpgradeStatus: Upgraded to xenial on 2017-05-15 (1127 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 09/17/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd09/17/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883681/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883681] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1883681/+attachment/5384338/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883681 Title: System freezes on specific kernel Status in linux package in Ubuntu: Incomplete Bug description: The servers will be running fine for some time and suddenly will freeze. It won't even respond to ping requests. We have to reboot the servers again to bring it back online but it won't be stable and will not respond again. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 15 17:52 seq crw-rw 1 root audio 116, 33 Jun 15 17:52 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=fe587596-cd68-4bbf-ae67-0e501fd6159c IwConfig: lono wireless extensions. ens160no wireless extensions. Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-184-generic root=/dev/mapper/cdns01--vg-root ro crashkernel=384M-:128M ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 RelatedPackageVersions: linux-restricted-modules-4.4.0-184-generic N/A linux-backports-modules-4.4.0-184-generic N/A linux-firmware 1.157.23 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-184-generic x86_64 UpgradeStatus: Upgraded to xenial on 2017-05-15 (1127 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 09/17/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd09/17/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883681/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883681] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1883681/+attachment/5384341/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883681 Title: System freezes on specific kernel Status in linux package in Ubuntu: Incomplete Bug description: The servers will be running fine for some time and suddenly will freeze. It won't even respond to ping requests. We have to reboot the servers again to bring it back online but it won't be stable and will not respond again. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 15 17:52 seq crw-rw 1 root audio 116, 33 Jun 15 17:52 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=fe587596-cd68-4bbf-ae67-0e501fd6159c IwConfig: lono wireless extensions. ens160no wireless extensions. Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-184-generic root=/dev/mapper/cdns01--vg-root ro crashkernel=384M-:128M ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 RelatedPackageVersions: linux-restricted-modules-4.4.0-184-generic N/A linux-backports-modules-4.4.0-184-generic N/A linux-firmware 1.157.23 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-184-generic x86_64 UpgradeStatus: Upgraded to xenial on 2017-05-15 (1127 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 09/17/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd09/17/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883681/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882195] Re: Dell Alienware Aurora R9 ubuntu 18.04LTS installation issue - Dual boot - UEFI
Please mark this as fixed. Not a bug Issue fixed. Bydefault 18.04 marked incorrect disk for the boot loader installation which caused the machine not boot properly. Due to this EFI mounts from secondary disk causing the booting issue. Marked the correct disk during installation by choosing bootloader fixed the issue Please mark this request as closed Notes:-for dual boot in Aurora R9 For Ubuntu 18.04 / 16.04 below is the fix from my side >From BIOS Disable secure boot, Storage AHCI mode Remove quiet and splash and add "nomodeset" from grub and install the OS. Mark correct disk from the bootloader list in the custom partitioning page On First boot, quiet and splash and add "nomodeset" and install the NVIDIA proprietary drivers preferably latest one ( 440 ) . Then reboot, it 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/1882195 Title: Dell Alienware Aurora R9 ubuntu 18.04LTS installation issue - Dual boot - UEFI Status in linux package in Ubuntu: Invalid Bug description: Issue:- Booting into recovery mode, after post installation Tried nomodeset parameters added in grub, able to install and post installation of NVIDIA-440 , machine booting in recovery mode. Note:- Ubuntu 20.04 LTS worked without any issues. Env:- Dell Alienware Aurora R9 Ubuntu 18.04.4 LTS 5.3.0-28-generic dosfstools 4.1-1 UEFI - Dual boot, secure boot disabled, SATA to AHCI Bios vers - 1.0.7 $lspci | grep VGA 01:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2080 SUPER] (rev a1) 02:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2080 SUPER] (rev a1) === Below is the journal logs, for the failure of machine boots into emergency mode. For some reasons, while unpacking the initramfs, it's unable to mount the EFI partition and dropping into emergency mode. And it's points bad superblock Might-be this is a bug in the 18.04. At the same time 20.04 worked without any issues. ~~~ Jun 07 17:08:32 test-Alienware-Aurora-R9 kernel: Initramfs unpacking failed: Decoding failed Jun 07 17:08:32 test-Alienware-Aurora-R9 kernel: Freeing initrd memory: 48284K Jun 07 17:08:33 test-Alienware-Aurora-R9 systemd[1]: Found device PM981a NVMe SAMSUNG 2048GB ESP. Jun 07 17:08:33 test-Alienware-Aurora-R9 systemd[1]: Starting File System Check on /dev/disk/by-uuid/CCF3-E7D6... Jun 07 17:08:33 test-Alienware-Aurora-R9 systemd[1]: Started File System Check Daemon to report status. Jun 07 17:08:33 test-Alienware-Aurora-R9 systemd[1]: Found device ST2000DM008-2FR102 4. Jun 07 17:08:33 test-Alienware-Aurora-R9 systemd[1]: Activating swap /dev/disk/by-uuid/5cfe5c2d-6dd7-46b3-9fce-0e08b35b26cb... Jun 07 17:08:33 test-Alienware-Aurora-R9 systemd[1]: Activated swap /dev/disk/by-uuid/5cfe5c2d-6dd7-46b3-9fce-0e08b35b26cb. Jun 07 17:08:33 test-Alienware-Aurora-R9 systemd[1]: Reached target Swap. Jun 07 17:08:33 test-Alienware-Aurora-R9 kernel: Adding 62499836k swap on /dev/sda4. Priority:-2 extents:1 across:62499836k FS Jun 07 17:08:33 test-Alienware-Aurora-R9 systemd-fsck[623]: fsck.fat 4.1 (2017-01-24) Jun 07 17:08:33 test-Alienware-Aurora-R9 systemd-fsck[623]: /dev/nvme0n1p1: 389 files, 36496/74752 clusters Jun 07 17:08:33 test-Alienware-Aurora-R9 systemd[1]: Started File System Check on /dev/disk/by-uuid/CCF3-E7D6. Jun 07 17:08:34 test-Alienware-Aurora-R9 systemd[1]: Mounting /boot/efi... Jun 07 17:08:34 test-Alienware-Aurora-R9 mount[669]: mount: /boot/efi: wrong fs type, bad option, bad superblock on /dev/nvme0n1p1, missing codepage or helper program, or other error. Jun 07 17:08:34 test-Alienware-Aurora-R9 systemd[1]: boot-efi.mount: Mount process exited, code=exited status=32 Jun 07 17:08:34 test-Alienware-Aurora-R9 systemd[1]: boot-efi.mount: Failed with result 'exit-code'. Jun 07 17:08:34 test-Alienware-Aurora-R9 systemd[1]: Failed to mount /boot/efi. Jun 07 17:08:34 test-Alienware-Aurora-R9 kernel: FAT-fs (nvme0n1p1): IO charset iso8859-1 not found Jun 07 17:08:34 test-Alienware-Aurora-R9 systemd[1]: Dependency failed for Local File Systems. Jun 07 17:08:34 test-Alienware-Aurora-R9 systemd[1]: Dependency failed for Clean up any mess left by 0dns-up. Jun 07 17:08:34 test-Alienware-Aurora-R9 systemd[1]: dns-clean.service: Job dns-clean.service/start failed with result 'dependency'. Jun 07 17:08:34 test-Alienware-Aurora-R9 systemd[1]: local-fs.target: Job local-fs.target/start failed with result 'dependency'. Jun 07 17:08:34 test-Alienware-Aurora-R9 systemd[1]: local-fs.target: Triggering OnFailure= dependencies. Jun 07 17:08:34 test-Alienware-Aurora-R9 systemd[1]: Starting Set console font and keymap... Jun 07 17:08:34 test-Alienware-Aurora-R9 systemd[1]: Started Stop ureadahead data collection 45s after completed startup. Jun 07 17:08:34 test-Alie
[Kernel-packages] [Bug 1882195] Re: Dell Alienware Aurora R9 ubuntu 18.04LTS installation issue - Dual boot - UEFI
Please mark this bug as fixed. This is not a bug ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882195 Title: Dell Alienware Aurora R9 ubuntu 18.04LTS installation issue - Dual boot - UEFI Status in linux package in Ubuntu: Invalid Bug description: Issue:- Booting into recovery mode, after post installation Tried nomodeset parameters added in grub, able to install and post installation of NVIDIA-440 , machine booting in recovery mode. Note:- Ubuntu 20.04 LTS worked without any issues. Env:- Dell Alienware Aurora R9 Ubuntu 18.04.4 LTS 5.3.0-28-generic dosfstools 4.1-1 UEFI - Dual boot, secure boot disabled, SATA to AHCI Bios vers - 1.0.7 $lspci | grep VGA 01:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2080 SUPER] (rev a1) 02:00.0 VGA compatible controller: NVIDIA Corporation TU104 [GeForce RTX 2080 SUPER] (rev a1) === Below is the journal logs, for the failure of machine boots into emergency mode. For some reasons, while unpacking the initramfs, it's unable to mount the EFI partition and dropping into emergency mode. And it's points bad superblock Might-be this is a bug in the 18.04. At the same time 20.04 worked without any issues. ~~~ Jun 07 17:08:32 test-Alienware-Aurora-R9 kernel: Initramfs unpacking failed: Decoding failed Jun 07 17:08:32 test-Alienware-Aurora-R9 kernel: Freeing initrd memory: 48284K Jun 07 17:08:33 test-Alienware-Aurora-R9 systemd[1]: Found device PM981a NVMe SAMSUNG 2048GB ESP. Jun 07 17:08:33 test-Alienware-Aurora-R9 systemd[1]: Starting File System Check on /dev/disk/by-uuid/CCF3-E7D6... Jun 07 17:08:33 test-Alienware-Aurora-R9 systemd[1]: Started File System Check Daemon to report status. Jun 07 17:08:33 test-Alienware-Aurora-R9 systemd[1]: Found device ST2000DM008-2FR102 4. Jun 07 17:08:33 test-Alienware-Aurora-R9 systemd[1]: Activating swap /dev/disk/by-uuid/5cfe5c2d-6dd7-46b3-9fce-0e08b35b26cb... Jun 07 17:08:33 test-Alienware-Aurora-R9 systemd[1]: Activated swap /dev/disk/by-uuid/5cfe5c2d-6dd7-46b3-9fce-0e08b35b26cb. Jun 07 17:08:33 test-Alienware-Aurora-R9 systemd[1]: Reached target Swap. Jun 07 17:08:33 test-Alienware-Aurora-R9 kernel: Adding 62499836k swap on /dev/sda4. Priority:-2 extents:1 across:62499836k FS Jun 07 17:08:33 test-Alienware-Aurora-R9 systemd-fsck[623]: fsck.fat 4.1 (2017-01-24) Jun 07 17:08:33 test-Alienware-Aurora-R9 systemd-fsck[623]: /dev/nvme0n1p1: 389 files, 36496/74752 clusters Jun 07 17:08:33 test-Alienware-Aurora-R9 systemd[1]: Started File System Check on /dev/disk/by-uuid/CCF3-E7D6. Jun 07 17:08:34 test-Alienware-Aurora-R9 systemd[1]: Mounting /boot/efi... Jun 07 17:08:34 test-Alienware-Aurora-R9 mount[669]: mount: /boot/efi: wrong fs type, bad option, bad superblock on /dev/nvme0n1p1, missing codepage or helper program, or other error. Jun 07 17:08:34 test-Alienware-Aurora-R9 systemd[1]: boot-efi.mount: Mount process exited, code=exited status=32 Jun 07 17:08:34 test-Alienware-Aurora-R9 systemd[1]: boot-efi.mount: Failed with result 'exit-code'. Jun 07 17:08:34 test-Alienware-Aurora-R9 systemd[1]: Failed to mount /boot/efi. Jun 07 17:08:34 test-Alienware-Aurora-R9 kernel: FAT-fs (nvme0n1p1): IO charset iso8859-1 not found Jun 07 17:08:34 test-Alienware-Aurora-R9 systemd[1]: Dependency failed for Local File Systems. Jun 07 17:08:34 test-Alienware-Aurora-R9 systemd[1]: Dependency failed for Clean up any mess left by 0dns-up. Jun 07 17:08:34 test-Alienware-Aurora-R9 systemd[1]: dns-clean.service: Job dns-clean.service/start failed with result 'dependency'. Jun 07 17:08:34 test-Alienware-Aurora-R9 systemd[1]: local-fs.target: Job local-fs.target/start failed with result 'dependency'. Jun 07 17:08:34 test-Alienware-Aurora-R9 systemd[1]: local-fs.target: Triggering OnFailure= dependencies. Jun 07 17:08:34 test-Alienware-Aurora-R9 systemd[1]: Starting Set console font and keymap... Jun 07 17:08:34 test-Alienware-Aurora-R9 systemd[1]: Started Stop ureadahead data collection 45s after completed startup. Jun 07 17:08:34 test-Alienware-Aurora-R9 systemd[1]: Reached target Timers. Jun 07 17:08:34 test-Alienware-Aurora-R9 systemd[1]: Closed Syslog Socket. Jun 07 17:08:34 test-Alienware-Aurora-R9 systemd[1]: Starting Set console scheme... Jun 07 17:08:34 test-Alienware-Aurora-R9 systemd[1]: Reached target Paths. Jun 07 17:08:34 test-Alienware-Aurora-R9 systemd[1]: Reached target Sockets. Jun 07 17:08:34 test-Alienware-Aurora-R9 systemd[1]: Started Emergency Shell. Jun 07 17:08:34 test-Alienware-Aurora-R9 systemd[1]: Reached target Emergency Mode. ~~~ We are able to boot even after passing "nomodeset" in grub This is a freshly installed machine, and tried with different kernels while
[Kernel-packages] [Bug 1883498] Re: Frequent Panic in ip6_expire_frag_queue->icmpv6_send on 4.4.0-184-generic
I can confirm that we experienced the same problem on one VM after upgrade from 4.4.0-179-generic to 4.4.0-184-generic last weekend. Since the rollback to the last working kernel this VM is running stable for over 25h now. Ubound Version 1.5.8 is also installed and running on this VM Don't have any crashdump, but the traceback looks the same: [ 1963.770497] BUG: unable to handle kernel NULL pointer dereference at 0018 [ 1963.781264] IP: [] icmp6_send+0x1fb/0x970 [ 1963.782881] PGD 0 [ 1963.783503] Oops: [#1] SMP [ 1963.784479] Modules linked in: binfmt_misc ip6t_REJECT nf_reject_ipv6 nf_log_ipv6 nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables ipt_REJECT nf_reject_ipv4 nf_log_ipv4 nf_log_common xt_LOG xt_limit xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_conntrack nf_conntrack iptable_filter ip_tables x_tables kvm_intel kvm irqbypass input_leds joydev serio_raw i2c_piix4 mac_hid 8250_fintek autofs4 qxl ttm drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops psmouse drm pata_acpi floppy [ 1963.794748] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 4.4.0-184-generic #214-Ubuntu [ 1963.796182] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS Bochs 01/01/2011 [ 1963.797696] task: 880236330d00 ti: 88023633c000 task.ti: 88023633c000 [ 1963.799081] RIP: 0010:[] [] icmp6_send+0x1fb/0x970 [ 1963.800628] RSP: 0018:88023fd03d00 EFLAGS: 00010246 [ 1963.801630] RAX: RBX: 8800bbad6700 RCX: 0020 [ 1963.802948] RDX: 0001 RSI: 0200 RDI: 880232c86a56 [ 1963.804281] RBP: 88023fd03e20 R08: R09: 880232c86a66 [ 1963.805625] R10: 0080 R11: R12: 880232c86a4e [ 1963.806951] R13: 81efb6c0 R14: 0001 R15: 0003 [ 1963.808399] FS: () GS:88023fd0() knlGS: [ 1963.809910] CS: 0010 DS: ES: CR0: 80050033 [ 1963.810987] CR2: 0018 CR3: 000234d7a000 CR4: 0670 [ 1963.812324] DR0: DR1: DR2: [ 1963.813662] DR3: DR6: fffe0ff0 DR7: 0400 [ 1963.815001] Stack: [ 1963.815395] 0001 23dc61b86a54e883 [ 1963.816889] 8802371b3a98 8802371b3ae0 371b3a80 880232c86a56 [ 1963.818372] 88020001 880232c86a66 [ 1963.819847] Call Trace: [ 1963.820317] [ 1963.820778] [] ? emulator_pio_in_emulated+0x1a0/0x1a0 [kvm] [ 1963.822192] [] ? notifier_call_chain+0x4c/0x70 [ 1963.823330] [] ? _raw_spin_unlock_bh+0x20/0x50 [ 1963.824475] [] icmpv6_send+0x21/0x30 [ 1963.825452] [] ip6_expire_frag_queue+0x115/0x1b0 [ 1963.826622] [] ? nf_ct_net_exit+0x50/0x50 [nf_defrag_ipv6] [ 1963.827951] [] nf_ct_frag6_expire+0x1f/0x30 [nf_defrag_ipv6] [ 1963.829365] [] call_timer_fn+0x37/0x140 [ 1963.830428] [] ? nf_ct_net_exit+0x50/0x50 [nf_defrag_ipv6] [ 1963.831826] [] run_timer_softirq+0x234/0x330 [ 1963.832958] [] __do_softirq+0x109/0x2b0 [ 1963.834002] [] irq_exit+0xa5/0xb0 [ 1963.834956] [] smp_apic_timer_interrupt+0x50/0x70 [ 1963.836164] [] apic_timer_interrupt+0xd4/0xe0 [ 1963.837292] [ 1963.837695] [] ? speculation_ctrl_update_tif+0x80/0x80 [ 1963.839394] [] ? native_safe_halt+0x12/0x20 [ 1963.840723] [] default_idle+0x1e/0xe0 [ 1963.841943] [] arch_cpu_idle+0x15/0x20 [ 1963.843171] [] default_idle_call+0x2a/0x40 [ 1963.844486] [] cpu_startup_entry+0x303/0x360 [ 1963.845822] [] start_secondary+0x177/0x1b0 [ 1963.847102] Code: 8b 5c 24 40 75 46 f6 c2 02 74 05 f6 c2 30 75 3c 48 8b 43 58 44 89 5c 24 34 89 54 24 40 44 89 44 24 48 4c 89 4c 24 60 48 83 e0 fe <48> 8b 78 18 e8 4c 0b 03 00 41 89 c2 4c 8b 4c 24 60 44 8b 44 24 [ 1963.852721] RIP [] icmp6_send+0x1fb/0x970 [ 1963.854022] RSP [ 1963.854896] CR2: 0018 [ 1963.857283] ---[ end trace e8d1fc7789e99b6a ]--- [ 1963.858369] Kernel panic - not syncing: Fatal exception in interrupt [ 1963.860271] Kernel Offset: disabled [ 1963.861149] ---[ end Kernel panic - not syncing: Fatal exception in interrupt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883498 Title: Frequent Panic in ip6_expire_frag_queue->icmpv6_send on 4.4.0-184-generic Status in linux package in Ubuntu: Confirmed Bug description: I happened to do an upgrade on a number of servers last week. Some of them got 4.4.0-179-generic and the ones upgraded a bit later during the week got 4.4.0-184-generic as it was just released. The ones with 4.4.0-184-generic started getting stuck. With linux-crashdump installed I obtained the dmesgs and crash dumps. The backtrace appears somewhat similar to #202669 but that one only happened on bare hardware for us - this one is on KVM virtual instan
[Kernel-packages] [Bug 1847982] Re: memcg_subgroup_charge from controllers in ubuntu_ltp failed on D/E
Didn't see this on E-AWS 5.3.0-1024.26 ARM64 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1847982 Title: memcg_subgroup_charge from controllers in ubuntu_ltp failed on D/E Status in ubuntu-kernel-tests: New Status in linux-azure package in Ubuntu: New Status in linux-kvm package in Ubuntu: New Status in linux-oracle package in Ubuntu: New Status in linux-azure source package in Disco: New Status in linux-kvm source package in Disco: New Status in linux-oracle source package in Disco: New Bug description: Issue found on Azure Disco kernel 5.0.0-1023.24 Failed on instance: * Standard_GS2 * Standard_D16s_v3 Passed on instance: * Standard_F32s_v2 * Standard_L8s_v2 * Standard_L4s * Standard_L8s_v2 (Although it has passed on these instances, but they all have the same test output, just the pids are different) Test failed with: /opt/ltp/testcases/bin/memcg_subgroup_charge.sh: 522: echo: echo: I/O error tag=memcg_subgroup_charge stime=1570239843 dur=3 exit=exited stat=1 core=no cu=7 cs=11 startup='Sat Oct 5 01:44:03 2019' memcg_subgroup_charge 1 TINFO: Starting test 1 /opt/ltp/testcases/bin/memcg_subgroup_charge.sh: 522: echo: echo: I/O error memcg_subgroup_charge 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_subgroup_charge 1 TINFO: Running memcg_process --mmap-anon -s 135168 memcg_subgroup_charge 1 TINFO: Warming up pid: 119041 memcg_subgroup_charge 1 TINFO: Process is still here after warm up: 119041 memcg_subgroup_charge 1 TPASS: rss is 135168 as expected memcg_subgroup_charge 2 TPASS: rss is 0 as expected memcg_subgroup_charge 3 TINFO: Starting test 2 /opt/ltp/testcases/bin/memcg_subgroup_charge.sh: 522: echo: echo: I/O error memcg_subgroup_charge 3 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_subgroup_charge 3 TINFO: Running memcg_process --mmap-anon -s 135168 memcg_subgroup_charge 3 TINFO: Warming up pid: 119071 memcg_subgroup_charge 3 TINFO: Process is still here after warm up: 119071 memcg_subgroup_charge 3 TFAIL: rss is 0, 135168 expected memcg_subgroup_charge 4 TPASS: rss is 0 as expected memcg_subgroup_charge 5 TINFO: Starting test 3 /opt/ltp/testcases/bin/memcg_subgroup_charge.sh: 522: echo: echo: I/O error memcg_subgroup_charge 5 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_subgroup_charge 5 TINFO: Running memcg_process --mmap-anon -s 135168 memcg_subgroup_charge 5 TINFO: Warming up pid: 119094 memcg_subgroup_charge 5 TINFO: Process is still here after warm up: 119094 memcg_subgroup_charge 5 TPASS: rss is 135168 as expected memcg_subgroup_charge 6 TPASS: rss is 0 as expected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1847982/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855817] Re: signal06 from ubuntu_ltp_syscalls failed on Eoan 5.3 GCP
Didn't see this on E-AWS (5.3.0-1024.26) with those instances mentioned in comment #1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1855817 Title: signal06 from ubuntu_ltp_syscalls failed on Eoan 5.3 GCP Status in ubuntu-kernel-tests: Fix Released Status in linux-gcp package in Ubuntu: Invalid Bug description: Issue found on 5.3.0-1010 Eoan GCP startup='Sat Dec 7 10:43:06 2019' signal06 0 TINFO : loop = 10771 signal06 1 TFAIL : signal06.c:87: Bug Reproduced! tag=signal06 stime=1575715386 dur=1 exit=exited stat=1 core=no cu=1 cs=3 This is not a regression as this failure can be found in 5.3.0-1009.10-gcp as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1855817/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855817] Re: signal06 from ubuntu_ltp_syscalls failed on Eoan 5.3 GCP
Didn't see this on Eoan GCP as well. Closing this. 5.3.0-1027.29-gcp ** Changed in: ubuntu-kernel-tests Status: New => Fix Released ** Changed in: linux-gcp (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1855817 Title: signal06 from ubuntu_ltp_syscalls failed on Eoan 5.3 GCP Status in ubuntu-kernel-tests: Fix Released Status in linux-gcp package in Ubuntu: Invalid Bug description: Issue found on 5.3.0-1010 Eoan GCP startup='Sat Dec 7 10:43:06 2019' signal06 0 TINFO : loop = 10771 signal06 1 TFAIL : signal06.c:87: Bug Reproduced! tag=signal06 stime=1575715386 dur=1 exit=exited stat=1 core=no cu=1 cs=3 This is not a regression as this failure can be found in 5.3.0-1009.10-gcp as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1855817/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883696] [NEW] Elantech ETPS/2 Touchpad not working despite correct drivers
Public bug reported: Although its recognised by the terminal and is enabled in settings the touchpad still doesnt work, Output of xinput in terminal ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ ETPS/2 Elantech Touchpad id=15 [slave pointer (2)] ⎜ ↳ MOSART Semi. 2.4G Keyboard Mouse Consumer Control id=11 [slave pointer (2)] ⎜ ↳ MOSART Semi. 2.4G Keyboard Mouse id=18 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Button id=8[slave keyboard (3)] ↳ HP TrueVision HD Camera: HP Tru id=13 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=14 [slave keyboard (3)] ↳ HP Wireless hotkeys id=16 [slave keyboard (3)] ↳ HP WMI hotkeysid=17 [slave keyboard (3)] ↳ MOSART Semi. 2.4G Keyboard Mouse id=9[slave keyboard (3)] ↳ MOSART Semi. 2.4G Keyboard Mouse System Control id=10 [slave keyboard (3)] ↳ MOSART Semi. 2.4G Keyboard Mouse Consumer Control id=12 [slave keyboard (3)] ssg-004@ssg-004-HP-Pavilion-Gaming-Laptop-15-ec0xxx:~$ xinput list-props 15 Device 'ETPS/2 Elantech Touchpad': Device Enabled (148): 1 Coordinate Transformation Matrix (150): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 libinput Tapping Enabled (303): 1 libinput Tapping Enabled Default (304): 0 libinput Tapping Drag Enabled (305):1 libinput Tapping Drag Enabled Default (306):1 libinput Tapping Drag Lock Enabled (307): 0 libinput Tapping Drag Lock Enabled Default (308): 0 libinput Tapping Button Mapping Enabled (309): 1, 0 libinput Tapping Button Mapping Default (310): 1, 0 libinput Natural Scrolling Enabled (285): 1 libinput Natural Scrolling Enabled Default (286): 0 libinput Disable While Typing Enabled (311):1 libinput Disable While Typing Enabled Default (312):1 libinput Scroll Methods Available (287):1, 1, 0 libinput Scroll Method Enabled (288): 0, 1, 0 libinput Scroll Method Enabled Default (289): 1, 0, 0 libinput Click Methods Available (313): 1, 1 libinput Click Method Enabled (314):1, 0 libinput Click Method Enabled Default (315):1, 0 libinput Middle Emulation Enabled (292):0 libinput Middle Emulation Enabled Default (293):0 libinput Accel Speed (294): 0.00 libinput Accel Speed Default (295): 0.00 libinput Left Handed Enabled (299): 0 libinput Left Handed Enabled Default (300): 0 libinput Send Events Modes Available (270): 1, 1 libinput Send Events Mode Enabled (271):0, 0 libinput Send Events Mode Enabled Default (272):0, 0 Device Node (273): "/dev/input/event10" Device Product ID (274):2, 14 libinput Drag Lock Buttons (301): libinput Horizontal Scroll Enabled (302): 1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-37-generic 5.4.0-37.41 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ssg-0041903 F pulseaudio /dev/snd/controlC1: ssg-0041903 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jun 16 12:15:08 2020 MachineType: HP HP Pavilion Gaming Laptop 15-ec0xxx ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=2fe214ae-e6c4-4797-b9a5-0d6ae3b63472 ro quiet splash i8042.kbdreset=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/06/2019 dmi.bios.vendor: AMI dmi.bios.version: F.05 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 86D4 dmi.board.vendor: HP dmi.board.version: 96.31 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.05:bd11/06/2019:svnHP:pnHPPavilionGamingLaptop15-ec0xxx:pvr:rvnHP:rn86D4:rvr96.31:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Gaming Laptop 15-ec0xxx dmi.product.sku: 8UM49EA#ABU dmi.sys.vendor: HP ** Affects: linux (Ubuntu) Importa
[Kernel-packages] [Bug 1861610] Re: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL'
Could you try a similar fix? https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881322/comments/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/1861610 Title: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL' Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.6 package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Status in linux-oem-5.6 source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Status in linux-oem-5.6 source package in Eoan: Invalid Status in linux-oem-osp1 source package in Eoan: Invalid Status in linux source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux-oem-osp1 source package in Focal: Invalid Bug description: [SRU Justification] [Impact] Touchpad function unavailable on some platforms with new ELAN touchpad HIDs. [Fix] https://lore.kernel.org/linux-input/000201d5a8bd$9fead3f0$dfc07bd0$@emc.com.tw/ required to match these currently unsupported IDs. [Test Case] 1. check if platform is affected, e.g. with ELAN0634: $ sudo acpidump | grep -C3 ELAN 2A060: 49 4E 54 31 70 0A 20 49 44 41 44 A4 84 53 42 46 INT1p.IDAD..SBF 2A070: 53 53 42 46 49 00 5B 82 42 0E 54 50 44 32 08 5F SSBFI.[.B.TPD2._ 2A080: 41 44 52 00 08 49 44 41 44 00 08 48 49 44 32 00 ADR..IDAD..HID2. 2A090: 08 5F 48 49 44 0D 45 4C 41 4E 30 36 33 34 00 08 ._HID.ELAN0634.. 2A0A0: 5F 43 49 44 0D 50 4E 50 30 43 35 30 00 08 5F 55 _CID.PNP0C50.._U 2A0B0: 49 44 01 14 4B 04 5F 44 53 4D 04 A0 3C 93 68 11 ID..K._DSM..<.h. 2A0C0: 13 0A 10 F7 F6 DF 3C 67 42 55 45 AD 05 B3 0A 3D ..https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861610/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883696] 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/1883696 Title: Elantech ETPS/2 Touchpad not working despite correct drivers Status in linux package in Ubuntu: Confirmed Bug description: Although its recognised by the terminal and is enabled in settings the touchpad still doesnt work, Output of xinput in terminal ⎜ ↳ Virtual core XTEST pointerid=4[slave pointer (2)] ⎜ ↳ ETPS/2 Elantech Touchpad id=15 [slave pointer (2)] ⎜ ↳ MOSART Semi. 2.4G Keyboard Mouse Consumer Control id=11 [slave pointer (2)] ⎜ ↳ MOSART Semi. 2.4G Keyboard Mouse id=18 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Button id=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Button id=8[slave keyboard (3)] ↳ HP TrueVision HD Camera: HP Tru id=13 [slave keyboard (3)] ↳ AT Translated Set 2 keyboard id=14 [slave keyboard (3)] ↳ HP Wireless hotkeys id=16 [slave keyboard (3)] ↳ HP WMI hotkeysid=17 [slave keyboard (3)] ↳ MOSART Semi. 2.4G Keyboard Mouse id=9[slave keyboard (3)] ↳ MOSART Semi. 2.4G Keyboard Mouse System Control id=10 [slave keyboard (3)] ↳ MOSART Semi. 2.4G Keyboard Mouse Consumer Control id=12 [slave keyboard (3)] ssg-004@ssg-004-HP-Pavilion-Gaming-Laptop-15-ec0xxx:~$ xinput list-props 15 Device 'ETPS/2 Elantech Touchpad': Device Enabled (148): 1 Coordinate Transformation Matrix (150): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 libinput Tapping Enabled (303): 1 libinput Tapping Enabled Default (304): 0 libinput Tapping Drag Enabled (305):1 libinput Tapping Drag Enabled Default (306):1 libinput Tapping Drag Lock Enabled (307): 0 libinput Tapping Drag Lock Enabled Default (308): 0 libinput Tapping Button Mapping Enabled (309): 1, 0 libinput Tapping Button Mapping Default (310): 1, 0 libinput Natural Scrolling Enabled (285): 1 libinput Natural Scrolling Enabled Default (286): 0 libinput Disable While Typing Enabled (311):1 libinput Disable While Typing Enabled Default (312):1 libinput Scroll Methods Available (287):1, 1, 0 libinput Scroll Method Enabled (288): 0, 1, 0 libinput Scroll Method Enabled Default (289): 1, 0, 0 libinput Click Methods Available (313): 1, 1 libinput Click Method Enabled (314):1, 0 libinput Click Method Enabled Default (315):1, 0 libinput Middle Emulation Enabled (292):0 libinput Middle Emulation Enabled Default (293):0 libinput Accel Speed (294): 0.00 libinput Accel Speed Default (295): 0.00 libinput Left Handed Enabled (299): 0 libinput Left Handed Enabled Default (300): 0 libinput Send Events Modes Available (270): 1, 1 libinput Send Events Mode Enabled (271):0, 0 libinput Send Events Mode Enabled Default (272):0, 0 Device Node (273): "/dev/input/event10" Device Product ID (274):2, 14 libinput Drag Lock Buttons (301): libinput Horizontal Scroll Enabled (302): 1 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-37-generic 5.4.0-37.41 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 NonfreeKernelModules: talpa_vfshook talpa_pedconnector talpa_pedevice talpa_vcdevice talpa_core talpa_linux talpa_syscallhook nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ssg-0041903 F pulseaudio /dev/snd/controlC1: ssg-0041903 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jun 16 12:15:08 2020 MachineType: HP HP Pavilion Gaming Laptop 15-ec0xxx ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=2fe214ae-e6c4-4797-b9a5-0d6ae3b63472 ro quiet splash i8042.kbdreset=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/06/2019 dmi.bios.vendor: AMI dmi
[Kernel-packages] [Bug 1848771]
While bysecting (I hope to complete tomorrow) I found a workaround (that works for me on Acer 720P). I always had tpm_tis.force=1 on the kernel command line. Now I added tpm_tis.interrupts=0. Wakes fine now with linux 5.6.0. Full command line: Kernel command line: BOOT_IMAGE=/@boot/vmlinuz-5.6.0-1011-oem root=UUID=17d2cd1d-cc37-446d-ac0b-933def63c867 ro rootflags=subvol=@ quiet splash tpm_tis.force=1 tpm_tis.interrupts=0 modprobe.blacklist=ehci_hcd,ehci-pci vt.handoff=7 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848771 Title: Reboot after resume from suspend (deep) Status in linux package in Ubuntu: Incomplete Status in ubuntu-release-upgrader package in Ubuntu: Invalid Bug description: After upgrading to Kubuntu Eoan (19.10) yesterday, my laptop crashes after resume from suspending. This is regardless the way of suspending (closing lid, selecting suspend from sddm, systemctl suspend). The journal shows: ferry@chromium:~$ journalctl -b -1 -e .. sddm[1106]: Message received from greeter: Suspend NetworkManager[836]: manager: sleep: sleep requested (sleeping: no enabled: yes) NetworkManager[836]: device (60:73:BC:BA:B8:68): state change: disconnected -> unmanaged (reason ' NetworkManager[836]: device (60:73:BC:23:8F:3E): state change: disconnected -> unmanaged (reason ' NetworkManager[836]: device (p2p-dev-wlp1s0): state change: disconnected -> unmanaged (reason 'sle NetworkManager[836]: manager: NetworkManager state is now ASLEEP systemd[1]: Reached target Sleep. systemd[1]: Starting Suspend... systemd-sleep[1238]: Suspending system... kernel: PM: suspend entry (deep) On resume (keypress, open lid) resume starts but immediately crashes and reboots. The laptop is an Acer 720p Chromebook with Chromium replaced and working fine with Kubuntu since 5 years or so. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: KDE Date: Fri Oct 18 18:45:53 2019 InstallationDate: Installed on 2017-07-13 (826 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848771/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848771]
(In reply to Ferry Toth from comment #41) > While bysecting (I hope to complete tomorrow) I found a workaround (that > works for me on Acer 720P). > > I always had tpm_tis.force=1 on the kernel command line. > Now I added tpm_tis.interrupts=0. > > Wakes fine now with linux 5.6.0. First of all, thanks for bisecting this! I can confirm setting tpm_tis.interrupts=0 works for me on ASUS C302 kernel 5.7.2 (Arch latest) and kernel 5.4.46 (Arch LTS). Previously I had no tpm_tis.interrupts setting so it must default to on. So the question is, why does tpm_tis.interrupts only cause problems on newer kernels? Is it a kernel bug? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848771 Title: Reboot after resume from suspend (deep) Status in linux package in Ubuntu: Incomplete Status in ubuntu-release-upgrader package in Ubuntu: Invalid Bug description: After upgrading to Kubuntu Eoan (19.10) yesterday, my laptop crashes after resume from suspending. This is regardless the way of suspending (closing lid, selecting suspend from sddm, systemctl suspend). The journal shows: ferry@chromium:~$ journalctl -b -1 -e .. sddm[1106]: Message received from greeter: Suspend NetworkManager[836]: manager: sleep: sleep requested (sleeping: no enabled: yes) NetworkManager[836]: device (60:73:BC:BA:B8:68): state change: disconnected -> unmanaged (reason ' NetworkManager[836]: device (60:73:BC:23:8F:3E): state change: disconnected -> unmanaged (reason ' NetworkManager[836]: device (p2p-dev-wlp1s0): state change: disconnected -> unmanaged (reason 'sle NetworkManager[836]: manager: NetworkManager state is now ASLEEP systemd[1]: Reached target Sleep. systemd[1]: Starting Suspend... systemd-sleep[1238]: Suspending system... kernel: PM: suspend entry (deep) On resume (keypress, open lid) resume starts but immediately crashes and reboots. The laptop is an Acer 720p Chromebook with Chromium replaced and working fine with Kubuntu since 5 years or so. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: KDE Date: Fri Oct 18 18:45:53 2019 InstallationDate: Installed on 2017-07-13 (826 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848771/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875456] Re: Azure diagnostic/serviceability improvement
** Changed in: linux-azure-4.15 (Ubuntu Bionic)
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/1875456
Title:
Azure diagnostic/serviceability improvement
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
Bug description:
Microsoft would like to request the inclusion of commits in all
releases supported on Azure. These commits will enable reporting 4
Kbytes of dmesg information to Hyper-V when Linux takes a panic.
Microsoft would like to get all releases reporting this information,
so that we can automatically get a rich picture of Linux panics in
Azure. This will limit the need get serial console logs or other
steps to manually acquire debug info.
We would like to request the folloiwng commits to enable the
diagnostic/serviceability improvement:
f3a99e761efa ("x86/Hyper-V: Report crash data in die() when panic_on_oops is
set")
040026df7088 ("x86/Hyper-V: Report crash register data when
sysctl_record_panic_msg is not set")
a11589563e96 ("x86/Hyper-V: Report crash register data or kmsg before running
crash kernel")
73f26e526f19 ("x86/Hyper-V: Trigger crash enlightenment only once during
system crash.")
7f11a2cc10a4 ("x86/Hyper-V: Free hv_panic_page when fail to register kmsg
dump")
74347a99e73a ("x86/Hyper-V: Unload vmbus channel in hv panic callback")
8afc06dd75c0 ("Drivers: hv: vmbus: Fix the issue with freeing up
hv_ctl_table_hdr")
ddcaf3ca4c3c ("Drivers: hv: vmus: Fix the check for return value from kmsg
get dump buffer")
81b18bce48af ("Drivers: HV: Send one page worth of kmsg dump over Hyper-V
during panic")
7ed4325a44ea ("Drivers: hv: vmbus: Make panic reporting to be more useful")
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1875456/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883681] Re: System freezes on specific kernel
Changing to confirmed as requested in comment #2. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883681 Title: System freezes on specific kernel Status in linux package in Ubuntu: Confirmed Bug description: The servers will be running fine for some time and suddenly will freeze. It won't even respond to ping requests. We have to reboot the servers again to bring it back online but it won't be stable and will not respond again. --- AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 15 17:52 seq crw-rw 1 root audio 116, 33 Jun 15 17:52 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=fe587596-cd68-4bbf-ae67-0e501fd6159c IwConfig: lono wireless extensions. ens160no wireless extensions. Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: VMware, Inc. VMware Virtual Platform Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen PATH=(custom, no user) LANG=en_US SHELL=/bin/bash ProcFB: 0 svgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-184-generic root=/dev/mapper/cdns01--vg-root ro crashkernel=384M-:128M ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223 RelatedPackageVersions: linux-restricted-modules-4.4.0-184-generic N/A linux-backports-modules-4.4.0-184-generic N/A linux-firmware 1.157.23 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-184-generic x86_64 UpgradeStatus: Upgraded to xenial on 2017-05-15 (1127 days ago) UserGroups: _MarkForUpload: True dmi.bios.date: 09/17/2015 dmi.bios.vendor: Phoenix Technologies LTD dmi.bios.version: 6.00 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvr6.00:bd09/17/2015:svnVMware,Inc.:pnVMwareVirtualPlatform:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A: dmi.product.name: VMware Virtual Platform dmi.product.version: None dmi.sys.vendor: VMware, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883681/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
Same thing here. In my case, the computer keeps booting into emergency mode, with output like in #5, and some additional ACPI errors. I changed COMPRESS to gzip as described in #47, but not back to lz4. Now the computer keeps booting into emergency mode with the message "/dev/sda2 clean" (which is my root partition). No more ACPI errors are reported. However, in emergency mode, I need to do "mount -a" each time and then "exit", otherwise it will return to emergency mode after FS check. The booting is quite slow, though. -- You 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 initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+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 1858495] Re: multiple long delays during kernel and userspace boot
The issue can't be reproduced anymore. ** Changed in: linux-signed-azure (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-azure in Ubuntu. https://bugs.launchpad.net/bugs/1858495 Title: multiple long delays during kernel and userspace boot Status in linux-signed-azure package in Ubuntu: Won't Fix Bug description: Booting some Bionic instances in Azure (gen1 machines), I see some large delays during kernel/userspace boot that it would be good to understand what's going on. Additionally, there areas during boot that see delays is different for an image that's been created from a template vs. stock images. I'm attaching some data, 10 runs of the same image in a scaling set that run the initial boot. Processing the journal output, looking at delays of over 2.0 shows some concern. [1.788581] localhost.localdomain kernel: * Found PM-Timer Bug on the chipset. Due to workarounds for a bug, * this clock source is slow. Consider trying other clock sources [3.545974] localhost.localdomain kernel: Unstable clock detected, switching default tracing clock to "global" If you want to keep using the local clock, then add: "trace_clock=local" on the kernel command line [6.401684] localhost.localdomain kernel: EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) [ 15.280390] localhost.localdomain kernel: EXT4-fs (sda1): re-mounted. Opts: discard After capturing bionic image as a template, and creating a new VM, we see new hot spots we didn't see before. # HotSpot maximum delta between kernel messages: 2.0 # [2.846188] localhost.localdomain kernel: AES CTR mode by8 optimization enabled # [5.919313] localhost.localdomain kernel: raid6: avx2x4 gen() 21512 MB/s # # [6.591530] localhost.localdomain kernel: EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null) # [9.031051] localhost.localdomain systemd[1]: systemd 237 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid) # # [ 13.773554] localhost.localdomain sh[871]: + exit 0 # [ 21.625467] localhost.localdomain kernel: UDF-fs: INFO Mounting volume 'UDF Volume', timestamp 2019/12/17 00:00 (1000) # # [ 24.919359] bugbif2be01 systemd-timesyncd[771]: Synchronized to time server 91.189.89.198:123 (ntp.ubuntu.com). # [ 29.787339] bugbif2be01 cloud-init[1026]: Cloud-init v. 19.2-36-g059d049c-0ubuntu2~18.04.1 running 'init' at Mon, 16 Dec 2019 18:14:47 +. Up 25.20 seconds. The easiest comparison kernel-side is the systemd-analyze value: Grepping in the debug data: % grep "Startup finished.*kernel" bug-bionic-baseline-no*.debug/*/journal.log | cut -d" " -f 7- Startup finished in 3.209s (kernel) + 49.305s (userspace) = 52.515s. Startup finished in 3.355s (kernel) + 51.732s (userspace) = 55.088s. Startup finished in 3.287s (kernel) + 51.747s (userspace) = 55.035s. Startup finished in 3.129s (kernel) + 50.066s (userspace) = 53.195s. Startup finished in 3.350s (kernel) + 50.682s (userspace) = 54.032s. Startup finished in 3.355s (kernel) + 49.322s (userspace) = 52.678s. Startup finished in 3.219s (kernel) + 51.124s (userspace) = 54.343s. Startup finished in 3.128s (kernel) + 49.226s (userspace) = 52.354s. Startup finished in 3.193s (kernel) + 53.197s (userspace) = 56.390s. Startup finished in 3.118s (kernel) + 46.203s (userspace) = 49.322s. foofoo % grep "Startup finished.*kernel" bug-bionic-baseline-after*.debug/*/journal.log | cut -d" " -f 7- Startup finished in 7.685s (kernel) + 32.463s (userspace) = 40.148s. Startup finished in 7.041s (kernel) + 35.998s (userspace) = 43.040s. Startup finished in 7.808s (kernel) + 35.444s (userspace) = 43.253s. Startup finished in 7.206s (kernel) + 37.952s (userspace) = 45.159s. Startup finished in 8.426s (kernel) + 36.976s (userspace) = 45.403s. Startup finished in 6.731s (kernel) + 35.484s (userspace) = 42.216s. Startup finished in 7.152s (kernel) + 32.664s (userspace) = 39.817s. Startup finished in 7.429s (kernel) + 36.177s (userspace) = 43.606s. Startup finished in 9.075s (kernel) + 32.494s (userspace) = 41.570s. Startup finished in 7.281s (kernel) + 32.732s (userspace) = 40.013s. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-1027-azure 5.0.0-1027.29~18.04.1 ProcVersionSignature: User Name 5.0.0-1027.29~18.04.1-azure 5.0.21 Uname: Linux 5.0.0-1027-azure x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: a
[Kernel-packages] [Bug 1850876] Re: CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan
@Ian, Did you add dtoverlay=vc4-fkms-v3d in the config.txt? This is the log on my board, looks like there is no error so far: ubuntu@ubuntu:~$ uname -a Linux ubuntu 5.3.0-1027-raspi2 #29++v3dv2 SMP Mon Jun 15 22:26:13 CST 2020 aarch64 aarch64 aarch64 GNU/Linux ubuntu@ubuntu:~$ dmesg | grep drm [3.759090] [drm] Initialized v3d 1.0.0 20180419 for fec0.v3d on minor 0 [3.790362] vc4-drm soc:gpu: bound fe60.firmwarekms (ops vc4_fkms_ops [vc4]) [3.798578] fb0: switching to vc4drmfb from simple [3.809972] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [3.816771] [drm] No driver support for vblank timestamp query. [3.822817] [drm] Setting vblank_disable_immediate to false because get_vblank_timestamp == NULL [3.866028] [drm] Initialized vc4 0.0.0 20140616 for soc:gpu on minor 1 [3.905537] [drm:vc4_crtc_mode_set_nofb [vc4]] *ERROR* couldn't fill AVI infoframe [4.031664] vc4-drm soc:gpu: fb0: vc4drmfb frame buffer device ubuntu@ubuntu:~$ lsmod | grep v3d v3d73728 0 gpu_sched 40960 1 v3d drm 516096 5 gpu_sched,drm_kms_helper,v3d,vc4 ubuntu@ubuntu:~$ ls /dev/dri/ -la total 0 drwxr-xr-x 3 root root120 Jun 16 12:03 . drwxr-xr-x 15 root root 18720 Jun 16 12:04 .. drwxr-xr-x 2 root root100 Jun 16 12:03 by-path crw-rw 1 root video 226, 0 Jun 16 12:03 card0 crw-rw 1 root video 226, 1 Jun 16 12:03 card1 crw-rw 1 root render 226, 128 Jun 16 12:03 renderD128 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1850876 Title: CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan Status in linux-raspi2 package in Ubuntu: Fix Released Status in linux-raspi2 source package in Eoan: Triaged Bug description: We enabled DRM_VC4 in the linux-raspi2 of eoan, but disabled the DRM_V3D. In fact the DRM_V3D is crucial for graphical applications (such as ubuntu-desktop :) as it removes the graphical overhead from the cpu to the gpu, making the applications work much faster. Please refer to https://bugs.launchpad.net/ubuntu/+source/linux- raspi2/+bug/1848703/comments/32 [Impact] Users reported that we should enable the DRM_V3D, then the GPU will be fully used when running "ubuntu-desktop" [Fix] Enable the DRM_V3D, the v3d.ko will be built [Test Case] Users already tested it, it worked well. https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848703/comments/36 [Regression Risk] Low, I already did building test for arm64 and armhf, all passed. And uers already tested the kernel module, it worked as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1850876/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883670] Re: Disable IEC958 on HP Thunderbolt Dock
The attachment "alsa-lib_1.2.2-2.3.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1883670 Title: Disable IEC958 on HP Thunderbolt Dock Status in HWE Next: New Status in alsa-lib package in Ubuntu: New Status in alsa-lib source package in Focal: New Status in alsa-lib source package in Groovy: New Bug description: [Impact] On HP Thunderbolt Dock, unusable SPDIF can be selected as output from PulseAudio. [Fix] Disable IEC958 (SPDIF) through ALSA UCM. [Test] With the UCM applied, `pactl` and audio panel in gnome-control-center no longer have SPDIF option. [Regression Potential] Low. This fix limits to the HP Thunderbolt Dock, other devices are unaffected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1883670/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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.
"If we edit /etc/initramfs-tools/initramfs.conf and COMPRESS=lz4, to COMPRESS=gzip then the error is fixing." Just changed it on a fresh install of 20.04 and the problem is still happening. -- You 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 1881810] Re: ZFS import cause panic
Thanks for you fast reply. This is the same behaviour from bug: 1880580, that I wrote. I have updated and can only continue verify on the latest 20.04, not 18.04 anymore. This is what I have done so far now. I tried you suggested solution. I first had to remove /etc/zfs/zpool.cache in order to be able to do this. Then I tried your solution 2 times, once with no flags, and then with -f flag. The panic still occurs when doing this. Should I try zdb again? Any other suggestions ? # cat /sys/module/zfs/parameters/spa_load_verify_metadata 1 # echo 0 | sudo tee /sys/module/zfs/parameters/spa_load_verify_metadata 0 # echo 0 | sudo tee /sys/module/zfs/parameters/spa_load_verify_data 0 # zpool import pool: datastore id: 3190464655986727485 state: ONLINE status: Some supported features are not enabled on the pool. action: The pool can be imported using its name or numeric identifier, though some features will not be available without an explicit 'zpool upgrade'. config: datastore ONLINE raidz2-0 ONLINE sdb ONLINE sdc ONLINE sdd ONLINE sde ONLINE sdf ONLINE sdg ONLINE # zpool import datastore or # zpool import -f datastore Cause this output: VERIFY3(c < SPA_MAXBLOCKSIZE >> SPA_MINBLOCKSHIFT) failed (...) PANIC at zio.c:293:zio_buf_alloc() -- 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/1881810 Title: ZFS import cause panic Status in zfs-linux package in Ubuntu: Triaged Bug description: 1) Ubuntu 20.04 LTS 2) apt policy zfsutils-linux zfsutils-linux: Installed: 0.8.3-1ubuntu12 Candidate:0.8.3-1ubuntu12 3) ZFS pool not possible to import, unless using read only. If trying to import normal way as write/read, casing panic message Expected to be able to import zpool without panic. Expected that scrub should not be able to run in read only. Expected that somehow be able to restore the zpool somehow. 4) # zpool status no pools available # zpool import pool: datastore id: 3190464655986727485 state: ONLINE status: Some supported features are not enabled on the pool. action: The pool can be imported using its name or numeric identifier, though some features will not be available without an explicit 'zpool upgrade'. config: datastore ONLINE raidz2-0 ONLINE sdb ONLINE sdc ONLINE sdd ONLINE sde ONLINE sdf ONLINE sdg ONLINE # zpool import -o readonly=on datastore # zpool status pool: datastore state: ONLINE status: Some supported features are not enabled on the pool. The pool can still be used, but some features are unavailable. action: Enable all features using 'zpool upgrade'. Once this is done, the pool may no longer be accessible by software that does not support the features. See zpool-features(5) for details. scan: scrub in progress since Sun May 10 00:24:01 2020 15,1T scanned at 0B/s, 15,1T issued at 0B/s, 15,1T total 1,44M repaired, 100,01% done, no estimated completion time config: NAMESTATE READ WRITE CKSUM datastore ONLINE 0 0 0 raidz2-0 ONLINE 0 0 0 sdb ONLINE 0 0 0 sdc ONLINE 0 0 0 sdd ONLINE 0 0 0 sde ONLINE 0 0 0 sdf ONLINE 0 0 0 sdg ONLINE 0 0 0 errors: No known data errors Running zdb it always stops ad 2,23T and then aborts. # zdb -e -bcsvL datastore Traversing all blocks to verify checksums ... 2.23T completed ( 149MB/s) estimated time remaining: 25hr 06min 25sec free(): invalid pointer Abort (SIGABRT) #zpool import datastore VERIFY3(c < SPA_MAXBLOCKSIZE >> SPA_MINBLOCKSHIFT) failed (36028797018963967 < 32768) PANIC at zio.c:293:zio_buf_alloc() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1881810/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1843385] Re: package nvidia-dkms-390 (not installed) failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status
I think I'm having the same issue as well, though due to a mysteriously broken 5.4.0 kernel (all of them in fact won't pass 'loading ramdisk' before system restart) I'm running version 4.15.0 on 20.04LTS whether or not that could be it I don't know. Apologies, I'm not a software person. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1843385 Title: package nvidia-dkms-390 (not installed) failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Bug description: Just upgraded the distro to 19.10 (dev) ProblemType: Package DistroRelease: Ubuntu 19.10 Package: nvidia-dkms-390 (not installed) ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9 Uname: Linux 5.2.0-15-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 Date: Tue Sep 10 08:08:26 2019 ErrorMessage: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 InstallationDate: Installed on 2016-02-03 (1314 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) Python3Details: /usr/bin/python3.7, Python 3.7.4+, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16+, python-minimal, 2.7.16-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.3 SourcePackage: nvidia-graphics-drivers-390 Title: package nvidia-dkms-390 (not installed) failed to install/upgrade: installed nvidia-dkms-390 package post-installation script subprocess returned error exit status 10 UpgradeStatus: Upgraded to eoan on 2019-09-10 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1843385/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850876] Re: CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan
ok after adding that line to the config.txt it works, but GNOME is glitching with multiple windows open, thats another issue though. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1850876 Title: CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan Status in linux-raspi2 package in Ubuntu: Fix Released Status in linux-raspi2 source package in Eoan: Triaged Bug description: We enabled DRM_VC4 in the linux-raspi2 of eoan, but disabled the DRM_V3D. In fact the DRM_V3D is crucial for graphical applications (such as ubuntu-desktop :) as it removes the graphical overhead from the cpu to the gpu, making the applications work much faster. Please refer to https://bugs.launchpad.net/ubuntu/+source/linux- raspi2/+bug/1848703/comments/32 [Impact] Users reported that we should enable the DRM_V3D, then the GPU will be fully used when running "ubuntu-desktop" [Fix] Enable the DRM_V3D, the v3d.ko will be built [Test Case] Users already tested it, it worked well. https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848703/comments/36 [Regression Risk] Low, I already did building test for arm64 and armhf, all passed. And uers already tested the kernel module, it worked as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1850876/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875665] Re: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04
** Changed in: rtkit (Ubuntu Focal) Assignee: (unassigned) => Seth Forshee (sforshee) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1875665 Title: rtkit-daemon[*]: Failed to make ourselves RT: Operation not permitted after upgrade to 20.04 Status in linux package in Ubuntu: Fix Committed Status in linux-azure package in Ubuntu: Invalid Status in linux-gcp package in Ubuntu: Invalid Status in linux-kvm package in Ubuntu: Invalid Status in linux-oracle package in Ubuntu: Invalid Status in linux-riscv package in Ubuntu: Invalid Status in rtkit package in Ubuntu: Confirmed Status in linux source package in Focal: Fix Released Status in linux-azure source package in Focal: Fix Released Status in linux-gcp source package in Focal: Fix Released Status in linux-kvm source package in Focal: Fix Released Status in linux-oracle source package in Focal: Fix Released Status in linux-riscv source package in Focal: Fix Released Status in rtkit source package in Focal: Confirmed Bug description: SRU Justification Impact: CONFIG_RT_GROUP_SCHED was enabled in focal, except for the lowlatency kernel since we expected most RT users to use that kernel. However we are getting RT regressions with the generic kernel. Digging deeper into this option, it seems to be pretty specialized and to require quite a bit of workload-specific configuration/tuning to be useful, so it doesn't really seem to make sense for a general-purpose kernel. Fix: Turn this option back off. Test Case: See comment #4. Regression Potential: This was turned on to support some docker functionality, so this functionality will no longer be available. We've had this option off for all releases prior to focal, so this seems acceptable. --- These errors started right after upgrading to 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: rtkit 0.12-4 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 28 10:31:43 2020 InstallationDate: Installed on 2019-06-18 (315 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) ProcEnviron: TERM=tmux-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rtkit UpgradeStatus: Upgraded to focal on 2020-04-21 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875665/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850876] Re: CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan
I just installed the ubuntu-desktop, and run glxinfo -B, it indicates the v3d is used, and run glxgears, it could run without any crash, looks like the v3d driver is more stable than before. And I already backported all v3d patches from rpi-5.4.x to ubuntu 5.3 kernel. I have no idea how to fix the issue of glitching with multiple windows open. BTW, how to check if the render links to llvmpipe or not? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1850876 Title: CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan Status in linux-raspi2 package in Ubuntu: Fix Released Status in linux-raspi2 source package in Eoan: Triaged Bug description: We enabled DRM_VC4 in the linux-raspi2 of eoan, but disabled the DRM_V3D. In fact the DRM_V3D is crucial for graphical applications (such as ubuntu-desktop :) as it removes the graphical overhead from the cpu to the gpu, making the applications work much faster. Please refer to https://bugs.launchpad.net/ubuntu/+source/linux- raspi2/+bug/1848703/comments/32 [Impact] Users reported that we should enable the DRM_V3D, then the GPU will be fully used when running "ubuntu-desktop" [Fix] Enable the DRM_V3D, the v3d.ko will be built [Test Case] Users already tested it, it worked well. https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848703/comments/36 [Regression Risk] Low, I already did building test for arm64 and armhf, all passed. And uers already tested the kernel module, it worked as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1850876/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883472] Re: linux-image-5.4.0-37-generic freezes on idle. linux-image-5.4.0-33-generic works fine.
Doing more testing, and now that I see this "feature" disabled, I don't think it always turned off the monitor. Looks like half of the time linux-image-5.4.0-33-generic failed to turn it off, but it still did NOT hang the entire system like linux-image-5.4.0-37-generic does. Monitor details $ sudo get-edid | parse-edid This is read-edid version 3.0.2. Prepare for some fun. Attempting to use i2c interface No EDID on bus 1 No EDID on bus 2 No EDID on bus 3 No EDID on bus 4 No EDID on bus 5 No EDID on bus 6 No EDID on bus 7 No EDID on bus 8 2 potential busses found: 0 9 Will scan through until the first EDID is found. Pass a bus number as an option to this program to go only for that one. Bus 0 doesn't really have an EDID... 128-byte EDID successfully retrieved from i2c bus 9 Looks like i2c was successful. Have a good day. Checksum Correct Section "Monitor" Identifier "DELL S2409W" ModelName "DELL S2409W" VendorName "DEL" # Monitor Manufactured week 22 of 2009 # EDID version 1.3 # Digital Display DisplaySize 530 300 Gamma 2.20 Option "DPMS" "true" Horizsync 30-83 VertRefresh 50-76 # Maximum pixel clock is 170MHz #Not giving standard mode: 1152x864, 75Hz #Not giving standard mode: 1280x1024, 60Hz #Not giving standard mode: 1920x1080, 60Hz Modeline"Mode 0" 148.50 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync EndSection -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1883472 Title: linux-image-5.4.0-37-generic freezes on idle. linux- image-5.4.0-33-generic works fine. Status in linux-signed package in Ubuntu: New Bug description: linux-image-5.4.0-33-generic Works OK linux-image-5.4.0-37-generic Freezes when leaving idle for some time. Ubuntu 20.04LTS 64 bits. Fully updated. Hardware: AMD Ryzen 7 1800X 32GB RAM (two sticks: Part number KHX2666C16/16G) Asus PRIME A320M-K - latest BIOS installed AMD Radeon R9 390X 8GB NVMe SSD 512GB (I don't recall the brand) Tried AMDGPU and RADEON drivers for the video card. The issue persists. I was not able to find any logs nor kernel panics on the usual log files. Booting the older kernel makes the machine work perfectly stable as before. Most of the time I come back to a black screen. Other times is partially dimmed, like when entering into power save mode, when the screensaver kicks in to shut down the monitor. WORKAROUND: Disabling the ability to shut down the monitor "fixes" the problem. In the xscreensaver settings I disabled quick power-off and also disabled power management, so it never tries to power off the monitor. Now the system is stable again. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1883472/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850876] Re: CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan
i dont have an idea, all i did to check was glxinfo | grep renderer -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1850876 Title: CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan Status in linux-raspi2 package in Ubuntu: Fix Released Status in linux-raspi2 source package in Eoan: Triaged Bug description: We enabled DRM_VC4 in the linux-raspi2 of eoan, but disabled the DRM_V3D. In fact the DRM_V3D is crucial for graphical applications (such as ubuntu-desktop :) as it removes the graphical overhead from the cpu to the gpu, making the applications work much faster. Please refer to https://bugs.launchpad.net/ubuntu/+source/linux- raspi2/+bug/1848703/comments/32 [Impact] Users reported that we should enable the DRM_V3D, then the GPU will be fully used when running "ubuntu-desktop" [Fix] Enable the DRM_V3D, the v3d.ko will be built [Test Case] Users already tested it, it worked well. https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848703/comments/36 [Regression Risk] Low, I already did building test for arm64 and armhf, all passed. And uers already tested the kernel module, it worked as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1850876/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877849] Re: conflicting packages while installing perf
Thanks fcole90. Possible duplicate of https://bugs.launchpad.net/ubuntu/+source/linux- oem-5.6/+bug/1881120 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1877849 Title: conflicting packages while installing perf Status in linux package in Ubuntu: Confirmed Bug description: I was trying to run perf, but I discovered it was not installed ``` $ perf stat -d so4/so-benchmark 100 Command 'perf' not found, but can be installed with: sudo apt install linux-oem-5.6-tools-common # version 5.6.0-1008.8, or sudo apt install linux-tools-common # version 5.4.0-29.33 ``` So I decided to install the latest version, so as `linux-oem-5.6-tools-common`. ``` $ sudo apt install linux-oem-5.6-tools-common Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: linux-oem-5.6-tools-common 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded. Need to get 174 kB of archives. After this operation, 395 kB of additional disk space will be used. Get:1 http://ubuntu.mirror.su.se/ubuntu focal-updates/main amd64 linux-oem-5.6-tools-common all 5.6.0-1008.8 [174 kB] Fetched 174 kB in 0s (446 kB/s) Selecting previously unselected package linux-oem-5.6-tools-common. (Reading database ... 326483 files and directories currently installed.) Preparing to unpack .../linux-oem-5.6-tools-common_5.6.0-1008.8_all.deb ... Progress: [ 0%] [.] Unpacking linux-oem-5.6-tools-common (5.6.0-1008.8) ...] Setting up linux-oem-5.6-tools-common (5.6.0-1008.8) ...#..] Progress: [ 60%] [#] Processing triggers for man-db (2.9.1-1) ...#..] ``` Then it finished, so I wanted to run perf finally. ``` $ perf stat -d so4/so-benchmark 100 WARNING: perf not found for kernel 5.4.0-28 You may need to install the following packages for this specific kernel: linux-tools-5.4.0-28-generic linux-cloud-tools-5.4.0-28-generic You may also want to install one of the following packages to keep up to date: linux-tools-generic linux-cloud-tools-generic ``` Ok, so I discover that my kernel is not compatible with version 5.6. But apt suggests to install one of those, so I pick `linux-tools- generic` so it stays up to date. ``` $ sudo apt install linux-tools-generic Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: linux-tools-5.4.0-29 linux-tools-5.4.0-29-generic linux-tools-common The following NEW packages will be installed: linux-tools-5.4.0-29 linux-tools-5.4.0-29-generic linux-tools-common linux-tools-generic 0 upgraded, 4 newly installed, 0 to remove and 0 not upgraded. Need to get 5 759 kB of archives. After this operation, 25,7 MB of additional disk space will be used. Do you want to continue? [Y/n] Y Get:1 http://ubuntu.mirror.su.se/ubuntu focal-updates/main amd64 linux-tools-common all 5.4.0-29.33 [186 kB] Get:2 http://ubuntu.mirror.su.se/ubuntu focal-updates/main amd64 linux-tools-5.4.0-29 amd64 5.4.0-29.33 [5 568 kB] Get:3 http://ubuntu.mirror.su.se/ubuntu focal-updates/main amd64 linux-tools-5.4.0-29-generic amd64 5.4.0-29.33 [1 988 B] Get:4 http://ubuntu.mirror.su.se/ubuntu focal-updates/main amd64 linux-tools-generic amd64 5.4.0.29.34 [2 604 B] Fetched 5 759 kB in 7s (878 kB/s) Selecting previously unselected package linux-tools-common. (Reading database ... 326549 files and directories currently installed.) Preparing to unpack .../linux-tools-common_5.4.0-29.33_all.deb ... Progress: [ 0%] [.] Unpacking linux-tools-common (5.4.0-29.33) ] dpkg: error processing archive /var/cache/apt/archives/linux-tools-common_5.4.0-29.33_all.deb (--unpack): trying to overwrite '/usr/bin/acpidbg', which is also in package linux-oem-5.6-tools-common 5.6.0-1008.8 dpkg-deb: error: paste subprocess was killed by signal (Broken pipe) Selecting previously unselected package linux-tools-5.4.0-29. Pre
[Kernel-packages] [Bug 1850876] Re: CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan
window glitching does not happen in XFCE, seems like a GNOME problem -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1850876 Title: CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan Status in linux-raspi2 package in Ubuntu: Fix Released Status in linux-raspi2 source package in Eoan: Triaged Bug description: We enabled DRM_VC4 in the linux-raspi2 of eoan, but disabled the DRM_V3D. In fact the DRM_V3D is crucial for graphical applications (such as ubuntu-desktop :) as it removes the graphical overhead from the cpu to the gpu, making the applications work much faster. Please refer to https://bugs.launchpad.net/ubuntu/+source/linux- raspi2/+bug/1848703/comments/32 [Impact] Users reported that we should enable the DRM_V3D, then the GPU will be fully used when running "ubuntu-desktop" [Fix] Enable the DRM_V3D, the v3d.ko will be built [Test Case] Users already tested it, it worked well. https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848703/comments/36 [Regression Risk] Low, I already did building test for arm64 and armhf, all passed. And uers already tested the kernel module, it worked as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1850876/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874444] Re: Bionic ubuntu ethtool doesn't check ring parameters boundaries
Hi Arthur, good news - there are currently Bionic and Xenial AMIs with
the fix! I've tried the following AMIs, and they have the fix:
ubuntu/images/hvm-ssd/ubuntu-bionic-18.04-amd64-server-20200610 -
ami-025201fa53cf4d031
ubuntu/images/hvm-ssd/ubuntu-xenial-16.04-amd64-server-20200610 -
ami-0a0ddd875a1ea2c7f
Note that the first one (Ubuntu 18.04) includes kernel 5.3, which contains the
fix.
Let me know if you have more questions, and thanks again for the report!
Cheers,
Guilherme
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/187
Title:
Bionic ubuntu ethtool doesn't check ring parameters boundaries
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Bug description:
[Impact]
* There's a bad behavior in the ena driver ringparam setting on kernels 4.4
and 4.15, if an invalid ringparam is provided to ethtool.
* Upstream Linux kernel implemented ring parameter boundaries check in
commit: 37e2d99b59c4 ("ethtool: Ensure new ring parameters are within bounds
during SRINGPARAM") [ git.kernel.org/linus/37e2d99b59c4 ].
Due to this commit, the community doesn't usually allow ring parameter
boundary checks in driver code.
* Xenial/Bionic kernels don't include this patch, and some network
drivers (like ena) rely on this patch for boundary checking of ring
params. So, we are hereby requesting the commit inclusion in these
kernel versions.
[Test case]
1. In AWS, create a new c5.4xlarge instance with the Ubuntu 18.04 official
ami (uses the ENA network driver) and update to latest kernel/reboot.
2. Run ethtool -g ens5
output:
Ring parameters for ens5:
Pre-set maximums:
RX: 16384
RX Mini: 0
RX Jumbo: 0
TX: 1024
Current hardware settings:
RX: 1024
RX Mini: 0
RX Jumbo: 0
TX: 1024
3. Change the TX/RX ring size to a legal number within boundaries -
works!
4. Change the TX/RX ring size to an illegal number (such as 2048 for
TX) with the command - "sudo ethtool -G ens5 tx 2048".
Expected behavior - "Cannot set device ring parameters: Invalid argument"
Actual behavior - causes a driver hang since boundaries are not checked by
ethtool, effectively hanging the instance (given that AWS has no console to
allow system manipulation).
[Regression Potential]
Since that the commit is present in kernels v4.16+ (including Ubuntu)
and is quite small and self-contained, the regression risk is very
reduced.
One potential "regression" would be if some driver has bugs and
provide bad values on get_ringparams, then the validation would be
broken (allowing illegal values or refusing legal ones), but this
wouldn't be a regression in the hereby proposed patch itself, it'd be
only exposed by the patch.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/187/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848921] Re: iwlwifi firmware crashes intel 9260ac [8086:2526] subsystem [8086:0010]
Yes, I think it is related to dual booting and the source of the problem might be indeed in the Windows driver leaving a setting on the card that the fw and driver in linux cannot cope with. Rebooting to linux from Windows causes a lot of trouble, but rebooting from linux to linux solves it. (Maybe after a couple of reboots until the card resets -no idea how this 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/1848921 Title: iwlwifi firmware crashes intel 9260ac [8086:2526] subsystem [8086:0010] Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 19.10 Kernel 5.3.0-18-generic Hardware: Thinkpad T460p (also tested on T480s) with Intel 9260ac wifi card. Expected: Wifi connects, uploads/downloads as normal Symptom: Wifi connects, as soon as an upload/download (any heavy traffic) start, the system comes to a crawl, becomes barely usable, and I end up opening a prompt to reboot. The system is unusable. This happens even with the Live USB version. The only solution I found was to download a different (newer) firmware. Latest version from: https://wireless.wiki.kernel.org/en/users/drivers/iwlwifi This is iwlwifi-9260-th-b0-jf-b0-34.618819.0.tgz I then manually copy the contained firmware to /lib/firmware, remove all other versions and make a link to iwlwifi-9260-th-b0-jf-46.ucode that the kernel expects to load. This completely resolves the issue. This is the carsh log (Thinkpad T460p, but identical to T480s, all fresh installs): Oct 20 01:51:13 weywot kernel: iwlwifi :03:00.0: Error sending SCAN_CFG_CMD: time out after 2000ms. Oct 20 01:51:13 weywot kernel: iwlwifi :03:00.0: Current CMD queue read_ptr 64 write_ptr 65 Oct 20 01:51:13 weywot kernel: iwlwifi :03:00.0: HW error, resetting before reading Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: Start IWL Error Log Dump: Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: Status: 0x0080, count: 609870115 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: Loaded firmware version: 46.6bf1df06.0 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x36BC8FCF | ADVANCED_SYSASSERT Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x28A5819E | trm_hw_status0 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x77944CFA | trm_hw_status1 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x018004F5 | branchlink2 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xEBCFC5F1 | interruptlink1 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x07206003 | interruptlink2 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xE956CDF4 | data1 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x7D692903 | data2 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xAD22F469 | data3 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x1040C00E | beacon time Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x0FF6877F | tsf low Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x82686A2F | tsf hi Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xB715D7B2 | time gp1 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x5EC31049 | time gp2 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xF7FD7FF6 | uCode revision type Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x31225172 | uCode version major Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xFD1DB8B4 | uCode version minor Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xC000F415 | hw version Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x7F9AFDD4 | board version Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xD5FD2F0F | hcmd Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x8F81D049 | isr0 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xEDDFDA7B | isr1 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xD9409AD7 | isr2 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x5AF7DA77 | isr3 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x400240BE | isr4 Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xEEF6DF6B | last cmd Id Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x40528540 | wait_event Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xB9BBD6FD | l2p_control Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xC21B6142 | l2p_duration Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x7BDF6F9E | l2p_mhvalid Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x190AF41B | l2p_addr_match Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x7FF297FF | lmpm_pmg_sel Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0x5248C715 | timestamp Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0: 0xBBB939AF | flow_handler Oct 20 01:51:16 weywot kernel: iwlwifi :03:00.0:
[Kernel-packages] [Bug 1883746] [NEW] brcmfmac won't connect to wpa2
Public bug reported: I am not able to get my wireless device to connect to an AP using WPA2 (personal). I can create an SSID with no security, and it can connect with no issues. 03:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM43602 802.11ac Wireless LAN SoC [14e4:43ba] (rev 01) Currently using built-in 'brcmfmac': https://wiki.debian.org/brcmfmac ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-37-generic 5.4.0-37.41 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: anthony 958 F pulseaudio /dev/snd/controlC0: anthony 958 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Jun 16 11:45:08 2020 InstallationDate: Installed on 2020-06-16 (0 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 002: ID 05ac:8406 Apple, Inc. Card Reader Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05ac:0273 Apple, Inc. Internal Keyboard/Trackpad (ISO) Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bluetooth Host Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=a9ab60c7-fc48-4fa7-87a6-f8991d613d9e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/2020 dmi.bios.vendor: Apple Inc. dmi.bios.version: 191.0.0.0.0 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvr191.0.0.0.0:bd04/16/2020:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug brcmfmac 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/1883746 Title: brcmfmac won't connect to wpa2 Status in linux package in Ubuntu: Confirmed Bug description: I am not able to get my wireless device to connect to an AP using WPA2 (personal). I can create an SSID with no security, and it can connect with no issues. 03:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM43602 802.11ac Wireless LAN SoC [14e4:43ba] (rev 01) Currently using built-in 'brcmfmac': https://wiki.debian.org/brcmfmac ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-37-generic 5.4.0-37.41 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: anthony 958 F pulseaudio /dev/snd/controlC0: anthony 958 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Jun 16 11:45:08 2020 InstallationDate: Installed on 2020-06-16 (0 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 002: ID 05ac:8406 Apple, Inc. Card Reader Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05ac:0273 Apple, Inc. Internal Keyboard/Trackpad (ISO) Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bluetooth Host Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=a9ab60c7-fc48-4fa7-87a6-f8991d613d9e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/2020 dmi.bios.vendor: Apple Inc. dmi.bios.version: 191.0.0.0.0 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvr191.0.0.0.0:bd04/16/2020:svnAppleInc.:pnMacBookPro12,1:pvr1.0
[Kernel-packages] [Bug 1883746] 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/1883746 Title: brcmfmac won't connect to wpa2 Status in linux package in Ubuntu: Confirmed Bug description: I am not able to get my wireless device to connect to an AP using WPA2 (personal). I can create an SSID with no security, and it can connect with no issues. 03:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM43602 802.11ac Wireless LAN SoC [14e4:43ba] (rev 01) Currently using built-in 'brcmfmac': https://wiki.debian.org/brcmfmac ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-37-generic 5.4.0-37.41 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: anthony 958 F pulseaudio /dev/snd/controlC0: anthony 958 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Jun 16 11:45:08 2020 InstallationDate: Installed on 2020-06-16 (0 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 002: ID 05ac:8406 Apple, Inc. Card Reader Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05ac:0273 Apple, Inc. Internal Keyboard/Trackpad (ISO) Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bluetooth Host Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=a9ab60c7-fc48-4fa7-87a6-f8991d613d9e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/2020 dmi.bios.vendor: Apple Inc. dmi.bios.version: 191.0.0.0.0 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvr191.0.0.0.0:bd04/16/2020:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883746/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883746] Re: brcmfmac with 14e4:43ba won't connect to wpa2
** Summary changed: - brcmfmac won't connect to wpa2 + brcmfmac with 14e4:43ba won't connect to wpa2 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883746 Title: brcmfmac with 14e4:43ba won't connect to wpa2 Status in linux package in Ubuntu: Confirmed Bug description: I am not able to get my wireless device to connect to an AP using WPA2 (personal). I can create an SSID with no security, and it can connect with no issues. 03:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM43602 802.11ac Wireless LAN SoC [14e4:43ba] (rev 01) Currently using built-in 'brcmfmac': https://wiki.debian.org/brcmfmac ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-37-generic 5.4.0-37.41 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: anthony 958 F pulseaudio /dev/snd/controlC0: anthony 958 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Tue Jun 16 11:45:08 2020 InstallationDate: Installed on 2020-06-16 (0 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 002: ID 05ac:8406 Apple, Inc. Card Reader Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05ac:0273 Apple, Inc. Internal Keyboard/Trackpad (ISO) Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bluetooth Host Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=a9ab60c7-fc48-4fa7-87a6-f8991d613d9e ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/16/2020 dmi.bios.vendor: Apple Inc. dmi.bios.version: 191.0.0.0.0 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvr191.0.0.0.0:bd04/16/2020:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883746/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877955] Comment bridged from LTC Bugzilla
--- Comment From naynj...@ibm.com 2020-06-16 13:03 EDT---
Hi,
I followed the steps from link -
https://wiki.ubuntu.com/Testing/EnableProposed
And have installed kernel:
5.4.0-38-generic for testing.
I am looking now for the key. I am not able to find one in this link -
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/proposed
Can you please share with me the gzip of the key.
Thanks & Regards,
- Nayna
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1877955
Title:
Fix for secure boot rules in IMA arch policy on powerpc
Status in The Ubuntu-power-systems project:
Fix Committed
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Groovy:
In Progress
Bug description:
SRU Justification:
==
[Impact]
* Currently the kernel module appended signature is verified twice
(finit_module) - once by the module_sig_check() and again by IMA.
* To prevent this the powerpc secure boot rules define an IMA
architecture specific policy rule only if CONFIG_MODULE_SIG_FORCE is
not enabled.
* But this doesn't take the ability into account of enabling
"sig_enforce" at the boot command line (module.sig_enforce=1).
* Including the IMA module appraise rule results in failing the
finit_module syscall, unless the module signing public key is loaded
onto the IMA keyring.
* This patch fixes secure boot policy rules to be based on
CONFIG_MODULE_SIG instead.
[Fix]
* fa4f3f56ccd28ac031ab275e673ed4098855fed4 fa4f3f56ccd2 "powerpc/ima:
Fix secure boot rules in ima arch policy"
[Test Case]
* Perform a secure boot on a powerpc system with
'module.sig_enforce=1' set at the boot command.
* If the IMA module appraise rule is included, the finit_module
syscall will fail (unless the module signing public key got loaded
onto the IMA keyring) without having the patch in place.
* The verification needs to be done by the IBM Power team.
[Regression Potential]
* There is (always) a certain regression risk with having code
changes, especially in the secure boot area.
* But this patch is limited to the powerpc platform and will not
affect any other architecture.
* It got discussed at
https://lore.kernel.org/r/1588342612-14532-1-git-send-email-na...@linux.ibm.com
before it became finally upstream accepted with kernel 5.7-rc7.
* The secure boot code itself wasn't really touched, rather than it's basis
for execution.
The IMA policy rule for module appraisal is now added only if
'CONFIG_MODULE_SIG' is not enabled (instead of CONFIG_MODULE_SIG_FORCE).
Hence the change is very limited and straightforward.
[Other]
* Since the patch got upstream with 5.7-rc7, it is already in groovy, hence
this SRU is for focal only.
__
== Comment: #0 - Michael Ranweiler - 2020-04-22
14:44:31 ==
+++ This bug was initially created as a clone of Bug #184073 +++
This bug is a follow on to LP 1866909 to address a missing piece -
only half the following patch was included in 5.4.0-24.28.
The upstream patch has an additional fix but it?s not critical for GA.
It can get included as part of bug fixes. It also affects only power.
The patch("powerpc/ima: fix secure boot rules in ima arch policy") is
posted to linux-integrity and linuxppc-dev mailing list
(https://lore.kernel.org/linux-integrity/1586549618-6106-1-git-send-
email-na...@linux.ibm.com/T/#u)
If there are any issues identified during further testing, they will
get opened as separate issue to be addressed later.
Thanks & Regards,
- Nayna
== Comment: #4 - Michael Ranweiler - 2020-05-11
02:23:35 ==
Updated posting:
https://lore.kernel.org/linux-integrity/1588342612-14532-1-git-send-
email-na...@linux.ibm.com/T/#u
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1877955/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881107] 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/1881107 Title: zfs: backport AES-GCM performance accelleration Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Focal: Fix Released Status in zfs-linux source package in Groovy: Fix Released Bug description: == SRU Justification == Upstream commit 31b160f0a6c673c8f926233af2ed6d5354808393 contains AES- GCM acceleration changes that significantly improve encrypted performance. Tests on a memory backed pool show performance improvements of ~15-22% for AES-CCM writes, ~17-20% AES-CCM reads, 34-36% AES-GCM writes and ~79-80% AES-GCM reads on a Sandybridge x86-64 CPU, so this looks like a promising optimization that will benefit a lot of users. == The fix == Backport of upstream 31b160f0a6c673c8f926233af2ed6d5354808393 - this is already backported in Groovy ZFS 0.8.3-1ubuntu13 == Test case == Run ZFS performance tests from ubuntu_performance_zfs_encryption ubuntu kernel team autotests. With the fix the encryption runs significantly faster, as noted earlier in the SRU justification. Also test with the 4 types of ZFS ubuntu autotests, should not fail any of these. == Regression Potential == This fix alters the crypto engine and adds in new optimizations for CPUs that have capable instruction sets. There is a risk that this new crypto code is erroneous. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1881107/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882624] Re: nested kvm doesn't not work
I tried to reproduce the issue with the latest 4.15.0-1089 kernel and the virtual machine started without issues. This bug might be the same as the one that was reported in bug 1881072, which was fixed in -1089. Do you mind validating this issue again now with the 4.15.0-1089? -- 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/1882624 Title: nested kvm doesn't not work Status in linux-azure package in Ubuntu: New Bug description: Create VM on Azure using Canonical UbuntuServer 14.04.5-LTS latest using size Standard E4s v3 Enable private-ppa canonical-kernel-esm Install kernel linux-azure, reboot VM, kernel version 4.15.0-1084-azure Install qemu-kvm, download https://eosgnestedstorage.blob.core.windows.net/images/nested- ubuntu-4.15.0-23-generic.qcow2 Launch nested VM using command qemu-system-x86_64 -smp 2 -m 2048 -hda /mnt/resource/nested.qcow2 -display none -device e1000,netdev=user.0 -netdev user,id=user.0,hostfwd=tcp::60022-:22 -enable-kvm -daemonize Expected ssh -p 60022 nesteduser@localhost will ask password to login We can't connect to it, see below call trace in dmesg qemu-kvm version doesn't change after kernel upgraded. 2.0.0+dfsg-2ubuntu1.46 [ 53.420589] hv_balloon: Max. dynamic memory size: 32768 MB [ 60.928772] L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/l1tf.html for details. [ 60.940895] kvm: SMP vm created on host with unstable TSC; guest TSC will not be reliable [ 60.967454] BUG: unable to handle kernel paging request at 56b8 [ 60.971140] IP: vmx_vcpu_run+0x3ed/0xbc0 [kvm_intel] [ 60.971140] PGD 0 P4D 0 [ 60.971140] Oops: [#1] SMP PTI [ 60.971140] Modules linked in: nf_conntrack_ipv4 nf_defrag_ipv4 xt_owner iptable_security xt_conntrack nf_conntrack libcrc32c ip_tables x_tables udf crc_itu_t dm_crypt joydev hid_generic kvm_intel kvm irqbypass hid_hyperv hid hyperv_keyboard hv_balloon serio_raw crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper cryptd hyperv_fb cfbfillrect pata_acpi cfbimgblt cfbcopyarea hv_netvsc hv_utils [ 60.971140] CPU: 2 PID: 1903 Comm: qemu-system-x86 Not tainted 4.15.0-1084-azure #94~14.04.1-Ubuntu [ 60.971140] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS 090007 06/02/2017 [ 60.971140] RIP: 0010:vmx_vcpu_run+0x3ed/0xbc0 [kvm_intel] [ 60.971140] RSP: 0018:a44847a53cc0 EFLAGS: 00010002 [ 60.971140] RAX: RBX: RCX: [ 61.020070] RDX: 6c14 RSI: RDI: [ 61.020070] RBP: a44847a53d10 R08: R09: [ 61.020070] R10: R11: R12: [ 61.020070] R13: R14: R15: [ 61.020070] FS: 7f753bba4700() GS:8fefdd68() knlGS: [ 61.020070] CS: 0010 DS: ES: CR0: 80050033 [ 61.020070] CR2: 56b8 CR3: 000888c42005 CR4: 003726e0 [ 61.020070] Call Trace: [ 61.020070] vcpu_enter_guest+0x909/0x12a0 [kvm] [ 61.020070] kvm_arch_vcpu_ioctl_run+0x2d8/0x3f0 [kvm] [ 61.020070] kvm_vcpu_ioctl+0x2a8/0x630 [kvm] [ 61.020070] ? dequeue_signal+0x3e/0x160 [ 61.020070] ? do_sigtimedwait+0xbd/0x210 [ 61.020070] ? copy_siginfo_to_user+0x12e/0x2d0 [ 61.020070] do_vfs_ioctl+0x9b/0x5f0 [ 61.020070] ? SyS_futex+0x71/0x150 [ 61.020070] SyS_ioctl+0x79/0x90 [ 61.020070] ? _copy_to_user+0x26/0x40 [ 61.020070] do_syscall_64+0x80/0x1e0 [ 61.020070] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [ 61.020070] RIP: 0033:0x7f7545f34ea7 [ 61.020070] RSP: 002b:7f753bba3bd8 EFLAGS: 0246 ORIG_RAX: 0010 [ 61.020070] RAX: ffda RBX: 7f754bbed000 RCX: 7f7545f34ea7 [ 61.020070] RDX: RSI: ae80 RDI: 000c [ 61.020070] RBP: 55c68fd7f160 R08: R09: 0002 [ 61.020070] R10: 0008 R11: 0246 R12: [ 61.020070] R13: R14: 7f753bba49c0 R15: 55c68ee809a0 [ 61.020070] Code: 31 ed 45 31 f6 45 31 ff 0f 20 d0 48 89 81 e0 02 00 00 31 c0 31 db 31 c9 31 d2 31 f6 31 ff 31 ed 5d 5a f6 05 0c c0 01 00 10 74 1b <48> 8b 81 b8 56 00 00 48 8b 40 40 48 8b 80 08 08 00 00 f6 c4 01 [ 61.020070] RIP: vmx_vcpu_run+0x3ed/0xbc0 [kvm_intel] RSP: a44847a53cc0 [ 61.020070] CR2: 56b8 [ 61.020070] ---[ end trace ab52be3a09d557f5 ]--- To manage notifications about this bug go to: https://bugs.lau
[Kernel-packages] [Bug 1881107] Re: zfs: backport AES-GCM performance accelleration
This bug was fixed in the package zfs-linux - 0.8.3-1ubuntu12.1
---
zfs-linux (0.8.3-1ubuntu12.1) focal; urgency=medium
* Backport AES-GCM performance accelleration (LP: #1881107)
- backport of upstream zfs commit 31b160f0a6c673c8f926233af2ed6d5354808393
("ICP: Improve AES-GCM performance").
tests on a memory backed pool show performance improvements of ~15-22%
for AES-CCM writes, ~17-20% AES-CCM reads, 34-36% AES-GCM writes and
~79-80% AES-GCM reads.
-- Colin Ian King Tue, 28 May 2020 11:54:33
+0100
** Changed in: zfs-linux (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1881107
Title:
zfs: backport AES-GCM performance accelleration
Status in zfs-linux package in Ubuntu:
Fix Released
Status in zfs-linux source package in Focal:
Fix Released
Status in zfs-linux source package in Groovy:
Fix Released
Bug description:
== SRU Justification ==
Upstream commit 31b160f0a6c673c8f926233af2ed6d5354808393 contains AES-
GCM acceleration changes that significantly improve encrypted
performance.
Tests on a memory backed pool show performance improvements of ~15-22%
for AES-CCM writes, ~17-20% AES-CCM reads, 34-36% AES-GCM writes and
~79-80% AES-GCM reads on a Sandybridge x86-64 CPU, so this looks like
a promising optimization that will benefit a lot of users.
== The fix ==
Backport of upstream 31b160f0a6c673c8f926233af2ed6d5354808393 - this
is already backported in Groovy ZFS 0.8.3-1ubuntu13
== Test case ==
Run ZFS performance tests from ubuntu_performance_zfs_encryption
ubuntu kernel team autotests. With the fix the encryption runs
significantly faster, as noted earlier in the SRU justification.
Also test with the 4 types of ZFS ubuntu autotests, should not fail
any of these.
== Regression Potential ==
This fix alters the crypto engine and adds in new optimizations for
CPUs that have capable instruction sets. There is a risk that this
new crypto code is erroneous.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1881107/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883773] [NEW] Disco update: upstream stable patchset 2020-06-16
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: upstream stable patchset 2020-06-16 from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883773 Title: Disco update: upstream stable patchset 2020-06-16 Status in linux package in Ubuntu: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2020-06-16 from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883773/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883774] 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/1883774 Title: wifi not working Status in linux package in Ubuntu: Confirmed Bug description: please help ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-37-generic 5.4.0-37.41 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yogi 1802 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 17 00:26:02 2020 InstallationDate: Installed on 2020-06-07 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 13d3:3526 IMC Networks Bluetooth Radio Bus 001 Device 003: ID 13d3:56c1 IMC Networks USB2.0 HD UVC WebCam Bus 001 Device 008: ID 1c9e:f101 OMEGA TECHNOLOGY JMR1040 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X430FA_S430FA ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=14d6c9b1-db09-4454-a28e-ca746a049802 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/28/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X430FA.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X430FA 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.:bvrX430FA.308:bd05/28/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX430FA_S430FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX430FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X430FA_S430FA 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/1883774/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883774] [NEW] wifi not working
Public bug reported: please help ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-37-generic 5.4.0-37.41 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yogi 1802 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 17 00:26:02 2020 InstallationDate: Installed on 2020-06-07 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 13d3:3526 IMC Networks Bluetooth Radio Bus 001 Device 003: ID 13d3:56c1 IMC Networks USB2.0 HD UVC WebCam Bus 001 Device 008: ID 1c9e:f101 OMEGA TECHNOLOGY JMR1040 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X430FA_S430FA ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=14d6c9b1-db09-4454-a28e-ca746a049802 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/28/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X430FA.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X430FA 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.:bvrX430FA.308:bd05/28/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX430FA_S430FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX430FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X430FA_S430FA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883774 Title: wifi not working Status in linux package in Ubuntu: Confirmed Bug description: please help ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-37-generic 5.4.0-37.41 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yogi 1802 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 17 00:26:02 2020 InstallationDate: Installed on 2020-06-07 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 13d3:3526 IMC Networks Bluetooth Radio Bus 001 Device 003: ID 13d3:56c1 IMC Networks USB2.0 HD UVC WebCam Bus 001 Device 008: ID 1c9e:f101 OMEGA TECHNOLOGY JMR1040 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X430FA_S430FA ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=14d6c9b1-db09-4454-a28e-ca746a049802 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/28/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X430FA.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X430FA 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.:bvrX430FA.308:bd05/28/2019:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX430FA_S430FA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX430FA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop X430FA_S430FA 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/1883774/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/List
[Kernel-packages] [Bug 1883773] Re: Disco update: upstream stable patchset 2020-06-16
** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + upstream stable patchset 2020-06-16 -upstream stable patchset 2020-06-16 -from git://git.kernel.org/ + Ported from the following upstream stable releases: + v4.19.127, v.5.4.45 + + from git://git.kernel.org/ + + Revert "cgroup: Add memory barriers to plug cgroup_rstat_updated() race window" + libnvdimm: Fix endian conversion issues + mm: Fix mremap not considering huge pmd devmap + HID: sony: Fix for broken buttons on DS3 USB dongles + HID: i2c-hid: add Schneider SCL142ALM to descriptor override + p54usb: add AirVasT USB stick device-id + kernel/relay.c: handle alloc_percpu returning NULL in relay_open + mmc: fix compilation of user API + scsi: ufs: Release clock if DMA map fails + net: dsa: mt7530: set CPU port to fallback mode + airo: Fix read overflows sending packets + drm/i915: fix port checks for MST support on gen >= 11 + powerpc/powernv: Avoid re-registration of imc debugfs directory + spi: dw: use "smp_mb()" to avoid sending spi data error + s390/ftrace: save traced function caller + ARC: Fix ICCM & DCCM runtime size checks + ARC: [plat-eznps]: Restrict to CONFIG_ISA_ARCOMPACT + evm: Fix RCU list related warnings + i2c: altera: Fix race between xfer_msg and isr thread + x86/mmiotrace: Use cpumask_available() for cpumask_var_t variables + net: bmac: Fix read of MAC address from ROM + drm/edid: Add Oculus Rift S to non-desktop list + s390/mm: fix set_huge_pte_at() for empty ptes + null_blk: return error for invalid zone size + net/ethernet/freescale: rework quiesce/activate for ucc_geth + net: ethernet: stmmac: Enable interface clocks on probe for IPQ806x + net: smsc911x: Fix runtime PM imbalance on error + HID: multitouch: add support for the Smart Tech panel + HID: multitouch: enable multi-input as a quirk for some devices + mt76: mt76x02u: Add support for newer versions of the XBox One wifi adapter + media: staging: ipu3-imgu: Move alignment attribute to field + ASoC: intel - fix the card names + selftests: mlxsw: qos_mc_aware: Specify arping timeout as an integer + UBUNTU: upstream stable to v4.19.127, v5.4.45 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883773 Title: Disco update: upstream stable patchset 2020-06-16 Status in linux package in Ubuntu: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2020-06-16 Ported from the following upstream stable releases: v4.19.127, v.5.4.45 from git://git.kernel.org/ Revert "cgroup: Add memory barriers to plug cgroup_rstat_updated() race window" libnvdimm: Fix endian conversion issues mm: Fix mremap not considering huge pmd devmap HID: sony: Fix for broken buttons on DS3 USB dongles HID: i2c-hid: add Schneider SCL142ALM to descriptor override p54usb: add AirVasT USB stick device-id kernel/relay.c: handle alloc_percpu returning NULL in relay_open mmc: fix compilation of user API scsi: ufs: Release clock if DMA map fails net: dsa: mt7530: set CPU port to fallback mode airo: Fix read overflows sending packets drm/i915: fix port checks for MST support on gen >= 11 powerpc/powernv: Avoid re-registration of imc debugfs directory spi: dw: use "smp_mb()" to avoid sending spi data error s390/ftrace: save traced function caller ARC: Fix ICCM & DCCM runtime size checks ARC: [plat-eznps]: Restrict to CONFIG_ISA_ARCOMPACT evm: Fix RCU list related warnings i2c: altera: Fix
[Kernel-packages] [Bug 1878351] Re: System shutdown directly by pressing power button and releasing immediately on Dell Vostro 5301
Right, the debouncer doesn't seem ideal. I'm not convinced either by upstream reply that forcing shutdown on another press is by design, imho we should try to convince them that it is wrong -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878351 Title: System shutdown directly by pressing power button and releasing immediately on Dell Vostro 5301 Status in OEM Priority Project: Incomplete Status in gnome-session package in Ubuntu: Triaged Status in linux package in Ubuntu: Confirmed Bug description: kchsieh@kchsieh-laptop:~$ lsb_release -rd Description: Ubuntu 20.04 LTS (fossa-bulbasaur X23) Release: 20.04 kchsieh@kchsieh-laptop:~$ apt-cache policy systemd systemd: Installed: 245.4-4ubuntu3 Candidate: 245.4-4ubuntu3 Version table: *** 245.4-4ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status Expect: When press the button, the endSeesionDialog should show up. Actual: The system shutdown directly. When the issue happend: endSessionDialog is not triggered immediately after the first power button event, but triggered after the second power button event. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-bulbasaur+X23 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-10 (3 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. Vostro 5301 Package: systemd 245.4-4ubuntu3 PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1010-oem root=UUID=b16fea1e-d8bc-4c71-a2e6-c43d269b40de ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1010.10-oem 5.6.8 Tags: focal Uname: Linux 5.6.0-1010-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/30/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.1.12 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.1.12:bd04/30/2020:svnDellInc.:pnVostro5301:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Vostro dmi.product.name: Vostro 5301 dmi.product.sku: 09FC dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1878351/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877955] Re: Fix for secure boot rules in IMA arch policy on powerpc
Hi, since 'proposed' belongs to the official archives
(archive.ubuntu.com/ubuntu) and packages from proposed are just located in a
special area there (we call it the proposed 'pocket'), kernels and other
packages from there that are signed, are signed with the standard and common
key.
Only a signed kernel that comes from a non-standard archive (like a PPA) is
signed with a different key, hence requires and additional key file.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1877955
Title:
Fix for secure boot rules in IMA arch policy on powerpc
Status in The Ubuntu-power-systems project:
Fix Committed
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Groovy:
In Progress
Bug description:
SRU Justification:
==
[Impact]
* Currently the kernel module appended signature is verified twice
(finit_module) - once by the module_sig_check() and again by IMA.
* To prevent this the powerpc secure boot rules define an IMA
architecture specific policy rule only if CONFIG_MODULE_SIG_FORCE is
not enabled.
* But this doesn't take the ability into account of enabling
"sig_enforce" at the boot command line (module.sig_enforce=1).
* Including the IMA module appraise rule results in failing the
finit_module syscall, unless the module signing public key is loaded
onto the IMA keyring.
* This patch fixes secure boot policy rules to be based on
CONFIG_MODULE_SIG instead.
[Fix]
* fa4f3f56ccd28ac031ab275e673ed4098855fed4 fa4f3f56ccd2 "powerpc/ima:
Fix secure boot rules in ima arch policy"
[Test Case]
* Perform a secure boot on a powerpc system with
'module.sig_enforce=1' set at the boot command.
* If the IMA module appraise rule is included, the finit_module
syscall will fail (unless the module signing public key got loaded
onto the IMA keyring) without having the patch in place.
* The verification needs to be done by the IBM Power team.
[Regression Potential]
* There is (always) a certain regression risk with having code
changes, especially in the secure boot area.
* But this patch is limited to the powerpc platform and will not
affect any other architecture.
* It got discussed at
https://lore.kernel.org/r/1588342612-14532-1-git-send-email-na...@linux.ibm.com
before it became finally upstream accepted with kernel 5.7-rc7.
* The secure boot code itself wasn't really touched, rather than it's basis
for execution.
The IMA policy rule for module appraisal is now added only if
'CONFIG_MODULE_SIG' is not enabled (instead of CONFIG_MODULE_SIG_FORCE).
Hence the change is very limited and straightforward.
[Other]
* Since the patch got upstream with 5.7-rc7, it is already in groovy, hence
this SRU is for focal only.
__
== Comment: #0 - Michael Ranweiler - 2020-04-22
14:44:31 ==
+++ This bug was initially created as a clone of Bug #184073 +++
This bug is a follow on to LP 1866909 to address a missing piece -
only half the following patch was included in 5.4.0-24.28.
The upstream patch has an additional fix but it?s not critical for GA.
It can get included as part of bug fixes. It also affects only power.
The patch("powerpc/ima: fix secure boot rules in ima arch policy") is
posted to linux-integrity and linuxppc-dev mailing list
(https://lore.kernel.org/linux-integrity/1586549618-6106-1-git-send-
email-na...@linux.ibm.com/T/#u)
If there are any issues identified during further testing, they will
get opened as separate issue to be addressed later.
Thanks & Regards,
- Nayna
== Comment: #4 - Michael Ranweiler - 2020-05-11
02:23:35 ==
Updated posting:
https://lore.kernel.org/linux-integrity/1588342612-14532-1-git-send-
email-na...@linux.ibm.com/T/#u
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1877955/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1734147] Re: corrupted BIOS due to Intel SPI bug in kernel
It worked! Thanks a lot! <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/1734147 Title: corrupted BIOS due to Intel SPI bug in kernel Status in Linux: Unknown Status in linux package in Ubuntu: Fix Released Status in linux-hwe-edge source package in Xenial: Fix Released Status in linux-oem source package in Xenial: Fix Released Status in linux source package in Artful: Fix Released Bug description: An update to linux kernel on Ubuntu 17.10 that enabled the Intel SPI drivers results in a serial flash that is read only in Intel Broadwell and Haswell machines with serial flashes with SPI_NOR_HAS_LOCK set. Symptoms: * BIOS settings cannot be saved * USB Boot impossible * EFI entries read-only. --- Fix: The issue was fixed in kernel version 4.13.0-21 by configuring the kernel so it is not compiled with Intel SPI support. But previous affected machines still suffered from a broken BIOS. Repair: If you still can boot into Ubuntu, you can recover your BIOS with the following steps: 1. Boot into Ubuntu 2. Download http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb 3. Install the downloaded package: $ sudo dpkg -i linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+20170103+1_amd64.deb 4. Make sure the kernel is installed without any error. Once installed, reboot. 5. At grub, choose the newly installed kernel. You can choose the "recovery" mode. 6. Reboot and go to BIOS settings to confirm your BIOS has been recovered. 7. In case your BIOS is not recovered, reboot to the new kernel, then reboot *once again* to the new kernel, do not enter BIOS settings before the reboot. After the second reboot, check BIOS. 8. If your BIOS issue remains, download another kernel from http://people.canonical.com/~ypwong/lp1734147/linux-image-4.15.0-041500rc6-generic_4.15.0-041500rc6.201712312330+clear+debug_amd64.deb, and use dpkg to install it, then repeat steps 4 to 6. After your BIOS is fixed, the kernel packages you just installed are no longer needed, you can remove it by running 'sudo dpkg -r linux- image-4.15.0-041500rc6-generic'. The patch used to build the linux v4.15 kernel in step 8 can be found at https://goo.gl/xUKJFR. If you have applied updates, and find that you can not boot the above fixed kernel because of Secure Boot and that the kernel is unsigned, but can still boot another kernel for your system; here's what you can do: 1) Download http://archive.ubuntu.com/ubuntu/dists/xenial/main/uefi/grub2-amd64/current/grubx64.efi.signed: $ wget http://archive.ubuntu.com/ubuntu/dists/xenial/main/uefi/grub2-amd64/current/grubx64.efi.signed 2) Copy grubx64.efi.signed over /boot/efi/EFI/ubuntu/grubx64.efi: $ sudo cp grubx64.efi.signed /boot/efi/EFI/ubuntu/grubx64.efi 3) Reboot; you should now be able to load the new unsigned kernel that allows fixing firmware / SPI. 4) Once you're satisfied that things work; boot to Ubuntu with a standard, signed kernel, and re-install the right GRUB version for your system: $ sudo grub-install --- Test Case: Fix has been verified by our HWE team on affected hardware. Regression Potential: Minimal, it's unlikely anyone is actually doing anything which requires this driver. --- Affected Machines: Lenovo B40-70 Lenovo B50-70 Lenovo B50-80 Lenovo Flex-3 Lenovo Flex-10 Lenovo G40-30 Lenovo G50-30 Lenovo G50-70 Lenovo G50-80 Lenovo S20-30 Lenovo U31-70 Lenovo Y50-70 Lenovo Y70-70 Lenovo Yoga Thinkpad (20C0) Lenovo Yoga 2 11" - 20332 Lenovo Yoga 3 11" Lenovo Z50-70 Lenovo Z51-70 Lenovo ideapad 100-15IBY Acer Aspire E5-771G Acer Aspire ES1-111M-C1LE (fixed following your new instruction (thank you)) Acer TravelMate B113 Acer Swift SF314-52 (Fixed by 4.14.9) Toshiba Satellite S55T-B5233 Toshiba Satellite L50-B-1R7 Toshiba Satellite S50-B-13G Toshiba Satellite L70-A-13M Dell Inspiron 15-3531 Mediacom Smartbook 14 Ultra M-SB14UC (fixed with official fix) Acer Aspire E3-111-C0UM HP 14-r012la --- Affected serial flash devices by manufacturer part number, JEDEC ID (SPI_NOR_HAS_LOCK set in drivers/mtd/spi-nor/spi-nor.c) /* ESMT */ f25l32pa, 0x8c2016 f25l32qa, 0x8c4116 f25l64qa, 0x8c4117 /* GigaDevice */ gd25q16, 0xc84015 gd25q32, 0xc84016 gd25lq32, 0xc86016 gd25q64, 0xc84017 gd25lq64c, 0xc86017 gd25q128, 0xc84018 gd25q256, 0xc84019 /* Winbond */ w25q16dw, 0xef6015 w25q32dw, 0xef6016 w25q64dw, 0xef6017 w25q128fw, 0xef6018 --- Original Description: Basically on Lenovo Y50-70 after installing Ubuntu 17.10, many users reported a corrupted BIOS. It's not possible to save new settings in BIOS anymore and after
[Kernel-packages] [Bug 1881339] Re: readdir performance when copying to userspace
When using a large directory with large names, I noticed a 50% increase in the time it took to readdir the entire directory. With small names, the increase did not seem noticeable enough. Tested on a VM with bionic, no SMAP involved. Compared before memchr and after memchr. Need to compare before and after uaccess changes, both without SMAP and with SMAP. Cascardo. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881339 Title: readdir performance when copying to userspace Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Triaged Status in linux source package in Bionic: In Progress Bug description: The following fixes were backported to bionic and xenial to prevent a potential security issue: - Make filldir[64]() verify the directory entry filename is valid - filldir[64]: remove WARN_ON_ONCE() for bad directory entries In that process, they introduced a potential performace impact on readdir. How much is yet to be measured. 9f79b78ef74436c7507bac6bfb7b8b989263bccb Convert filldir[64]() from __put_user() to unsafe_put_user() c512c69187197fe08026cb5bbe7b9709f4f89b73 uaccess: implement a proper unsafe_copy_to_user() and switch filldir over to it The two commits above try to mitigate that performance impact. At least on x86 with SMAP, that should have some effect. At any other platforms, at least on bionic and xenial, any improvements should be measured. Though that is true for x86 with SMAP too. This bug is opened in order to keep track of that possible performance improvement we might add in the future as followup for those two commits. Cascardo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881339/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883780] Re: Problems with module rt2800 and falling connection
** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883780/+attachment/5384527/+files/lspci-vnvn.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883780 Title: Problems with module rt2800 and falling connection Status in linux package in Ubuntu: Confirmed Bug description: Com o kernel: 5.4.0.37 Gnome: 3.36 Versão: 20.04 LTS Network Manager: 1.22.10 A configuração que eu tentei em rt2800pci.conf em /etc/modprobe.d/ options rt2800pci nohwcrypt = 1 Não resolvido Connect for a period and then disconnect. Leaving the connection unstable. Suspeito que este módulo esteja causando superaquecimento na máquina, porque se eu executar o modprobe -r rt2800pci, a máquina não superaquecerá tanto quanto quando carrego este módulo. Quedas freqüentes de conexão ocorrem e, às vezes, nem funcionam. QUERO DESTACAR QUE ISSO SÓ OCORRE COM A UBUNTU, OUTRAS DISTRIBUIÇÕES QUE USAM ESTE KERNEL NÃO OCORREM ESTAS QUEDAS DE CONEXÃO QUE ESTOU RELATANDO. 00: 00.0 Ponte host: Controladora DRAM do processador principal Intel Corporation (rev 02) 00: 01.0 Ponte PCI: Processador principal Intel Corporation Porta raiz PCI Express x16 (rev 02) 00: 16.0 Controlador de comunicação: Intel Corporation série 5/3400 chipset HECI Controlador (rev 06) 00: 1a.0 Controlador USB: chipset Intel Corporation série 5/3400 Series Controlador host USB2 aprimorado (rev 05) 00: 1b.0 Dispositivo de áudio: Áudio Intel de alta definição Chipset série 5 da série Intel / 3400 (rev 05) Ponte PCI 00: 1c.0: Porta raiz 1 do PCI Express Intel Chipset série 5/3400 Series (rev 05) Ponte PCI 00: 1c.1: Porta raiz 2 do chipset Intel Corporation série 5/3400 (rev) 05) 00: 1c.4 Ponte PCI: Intel Corporation Série 5/3400 Chipset PCI Express Root Port 5 (rev 05) 00: 1d.0 Controlador USB: Intel Corporation série 5/3400 Series Chipset Controlador host avançado USB2 (rev 05) 00 : 1e.0 ponte PCI: Intel Corporation 82801 Mobile PCI Bridge (rev a5) 00: 1f.0 ponte ISA: Intel Corporation HM55 Chipset LPC Interface Controller (rev 05) 00: 1f.2 SATA controller: Intel Corporation 5 Series / 3400 Controlador SATA AHCI da porta 4 do chipset série 4 (rev 05) 00: 1f.3 SMBus: Intel Corporation Série 5/3400 Controlador SMBus do chipset série 5 (rev 05) 00: 1f.6 Controlador de processamento de sinal: Chipset Intel série 5 série / 3400 Intel Thermal Subsistema (rev. 05) 01: 00.0 Controlador compatível com VGA: NVIDIA Corporation GT218M [GeForce 310M] (rev a2) 01: 00.1 Dispositivo de áudio: Controlador de áudio de alta definição NVIDIA Corporation (rev a1) 02: 00.0 Controlador de rede: Ralink corp. RT3090 Controlador Ethernet 802.11n 1T / 1R PCIe 03: 00.0 Ethernet: Realtek Semiconductor Co., Ltd. RTL8111 / 8168/8411 Controlador Ethernet Gigabit PCI Express (rev 06) 3f: 00.0 Ponte do host: Intel Corporation Core Processor Core QuickPath Architecture Genérico não- registradores principais (rev 02) 3f: 00.1 Bridge host: decodificador de endereços do sistema de arquitetura do processador central Intel Corporation QuickPath (rev 02) 3f: 02.0 Bridge host: processador Intel Corporation QPI Link 0 (rev 02) 3f: 02.1 Ponte do host: Intel Corporation 1ª geração do processador Core i3 / 5/7 QPI físico 0 (rev 02) 3f: 02.2 Ponte do host: Intel Corporation 1ª geração do processador Core i3 / 5/7 reservado (rev 02) 3f: 02.3 host bridge: Processador Intel Corporation de primeira geração Core i3 / 5/7 reservado (rev 02) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883780/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883780] [NEW] Problems with module rt2800 and falling connection
Public bug reported: Com o kernel: 5.4.0.37 Gnome: 3.36 Versão: 20.04 LTS Network Manager: 1.22.10 A configuração que eu tentei em rt2800pci.conf em /etc/modprobe.d/ options rt2800pci nohwcrypt = 1 Não resolvido Connect for a period and then disconnect. Leaving the connection unstable. Suspeito que este módulo esteja causando superaquecimento na máquina, porque se eu executar o modprobe -r rt2800pci, a máquina não superaquecerá tanto quanto quando carrego este módulo. Quedas freqüentes de conexão ocorrem e, às vezes, nem funcionam. QUERO DESTACAR QUE ISSO SÓ OCORRE COM A UBUNTU, OUTRAS DISTRIBUIÇÕES QUE USAM ESTE KERNEL NÃO OCORREM ESTAS QUEDAS DE CONEXÃO QUE ESTOU RELATANDO. 00: 00.0 Ponte host: Controladora DRAM do processador principal Intel Corporation (rev 02) 00: 01.0 Ponte PCI: Processador principal Intel Corporation Porta raiz PCI Express x16 (rev 02) 00: 16.0 Controlador de comunicação: Intel Corporation série 5/3400 chipset HECI Controlador (rev 06) 00: 1a.0 Controlador USB: chipset Intel Corporation série 5/3400 Series Controlador host USB2 aprimorado (rev 05) 00: 1b.0 Dispositivo de áudio: Áudio Intel de alta definição Chipset série 5 da série Intel / 3400 (rev 05) Ponte PCI 00: 1c.0: Porta raiz 1 do PCI Express Intel Chipset série 5/3400 Series (rev 05) Ponte PCI 00: 1c.1: Porta raiz 2 do chipset Intel Corporation série 5/3400 (rev) 05) 00: 1c.4 Ponte PCI: Intel Corporation Série 5/3400 Chipset PCI Express Root Port 5 (rev 05) 00: 1d.0 Controlador USB: Intel Corporation série 5/3400 Series Chipset Controlador host avançado USB2 (rev 05) 00 : 1e.0 ponte PCI: Intel Corporation 82801 Mobile PCI Bridge (rev a5) 00: 1f.0 ponte ISA: Intel Corporation HM55 Chipset LPC Interface Controller (rev 05) 00: 1f.2 SATA controller: Intel Corporation 5 Series / 3400 Controlador SATA AHCI da porta 4 do chipset série 4 (rev 05) 00: 1f.3 SMBus: Intel Corporation Série 5/3400 Controlador SMBus do chipset série 5 (rev 05) 00: 1f.6 Controlador de processamento de sinal: Chipset Intel série 5 série / 3400 Intel Thermal Subsistema (rev. 05) 01: 00.0 Controlador compatível com VGA: NVIDIA Corporation GT218M [GeForce 310M] (rev a2) 01: 00.1 Dispositivo de áudio: Controlador de áudio de alta definição NVIDIA Corporation (rev a1) 02: 00.0 Controlador de rede: Ralink corp. RT3090 Controlador Ethernet 802.11n 1T / 1R PCIe 03: 00.0 Ethernet: Realtek Semiconductor Co., Ltd. RTL8111 / 8168/8411 Controlador Ethernet Gigabit PCI Express (rev 06) 3f: 00.0 Ponte do host: Intel Corporation Core Processor Core QuickPath Architecture Genérico não- registradores principais (rev 02) 3f: 00.1 Bridge host: decodificador de endereços do sistema de arquitetura do processador central Intel Corporation QuickPath (rev 02) 3f: 02.0 Bridge host: processador Intel Corporation QPI Link 0 (rev 02) 3f: 02.1 Ponte do host: Intel Corporation 1ª geração do processador Core i3 / 5/7 QPI físico 0 (rev 02) 3f: 02.2 Ponte do host: Intel Corporation 1ª geração do processador Core i3 / 5/7 reservado (rev 02) 3f: 02.3 host bridge: Processador Intel Corporation de primeira geração Core i3 / 5/7 reservado (rev 02) ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Attachment added: "log" https://bugs.launchpad.net/bugs/1883780/+attachment/5384519/+files/lspci-vnvn.log ** Summary changed: - Frequent crashes of conection occur with the rt2800pci module + Problems with module rt2800 and crash connection ** Summary changed: - Problems with module rt2800 and crash connection + Problems with module rt2800 and falling connection ** 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/1883780 Title: Problems with module rt2800 and falling connection Status in linux package in Ubuntu: Confirmed Bug description: Com o kernel: 5.4.0.37 Gnome: 3.36 Versão: 20.04 LTS Network Manager: 1.22.10 A configuração que eu tentei em rt2800pci.conf em /etc/modprobe.d/ options rt2800pci nohwcrypt = 1 Não resolvido Connect for a period and then disconnect. Leaving the connection unstable. Suspeito que este módulo esteja causando superaquecimento na máquina, porque se eu executar o modprobe -r rt2800pci, a máquina não superaquecerá tanto quanto quando carrego este módulo. Quedas freqüentes de conexão ocorrem e, às vezes, nem funcionam. QUERO DESTACAR QUE ISSO SÓ OCORRE COM A UBUNTU, OUTRAS DISTRIBUIÇÕES QUE USAM ESTE KERNEL NÃO OCORREM ESTAS QUEDAS DE CONEXÃO QUE ESTOU RELATANDO. 00: 00.0 Ponte host: Controladora DRAM do processador principal Intel Corporation (rev 02) 00: 01.0 Ponte PCI: Processador principal Intel Corporation Porta raiz PCI Express x16 (rev 02) 00: 16.0 Controlador de comunicação: Intel Corporation série 5/3400 chipset HECI Controlador (rev 06) 00:
[Kernel-packages] [Bug 1883780] Re: Problems with module rt2800 and falling connection
** Attachment added: "version.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883780/+attachment/5384526/+files/version.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883780 Title: Problems with module rt2800 and falling connection Status in linux package in Ubuntu: Confirmed Bug description: Com o kernel: 5.4.0.37 Gnome: 3.36 Versão: 20.04 LTS Network Manager: 1.22.10 A configuração que eu tentei em rt2800pci.conf em /etc/modprobe.d/ options rt2800pci nohwcrypt = 1 Não resolvido Connect for a period and then disconnect. Leaving the connection unstable. Suspeito que este módulo esteja causando superaquecimento na máquina, porque se eu executar o modprobe -r rt2800pci, a máquina não superaquecerá tanto quanto quando carrego este módulo. Quedas freqüentes de conexão ocorrem e, às vezes, nem funcionam. QUERO DESTACAR QUE ISSO SÓ OCORRE COM A UBUNTU, OUTRAS DISTRIBUIÇÕES QUE USAM ESTE KERNEL NÃO OCORREM ESTAS QUEDAS DE CONEXÃO QUE ESTOU RELATANDO. 00: 00.0 Ponte host: Controladora DRAM do processador principal Intel Corporation (rev 02) 00: 01.0 Ponte PCI: Processador principal Intel Corporation Porta raiz PCI Express x16 (rev 02) 00: 16.0 Controlador de comunicação: Intel Corporation série 5/3400 chipset HECI Controlador (rev 06) 00: 1a.0 Controlador USB: chipset Intel Corporation série 5/3400 Series Controlador host USB2 aprimorado (rev 05) 00: 1b.0 Dispositivo de áudio: Áudio Intel de alta definição Chipset série 5 da série Intel / 3400 (rev 05) Ponte PCI 00: 1c.0: Porta raiz 1 do PCI Express Intel Chipset série 5/3400 Series (rev 05) Ponte PCI 00: 1c.1: Porta raiz 2 do chipset Intel Corporation série 5/3400 (rev) 05) 00: 1c.4 Ponte PCI: Intel Corporation Série 5/3400 Chipset PCI Express Root Port 5 (rev 05) 00: 1d.0 Controlador USB: Intel Corporation série 5/3400 Series Chipset Controlador host avançado USB2 (rev 05) 00 : 1e.0 ponte PCI: Intel Corporation 82801 Mobile PCI Bridge (rev a5) 00: 1f.0 ponte ISA: Intel Corporation HM55 Chipset LPC Interface Controller (rev 05) 00: 1f.2 SATA controller: Intel Corporation 5 Series / 3400 Controlador SATA AHCI da porta 4 do chipset série 4 (rev 05) 00: 1f.3 SMBus: Intel Corporation Série 5/3400 Controlador SMBus do chipset série 5 (rev 05) 00: 1f.6 Controlador de processamento de sinal: Chipset Intel série 5 série / 3400 Intel Thermal Subsistema (rev. 05) 01: 00.0 Controlador compatível com VGA: NVIDIA Corporation GT218M [GeForce 310M] (rev a2) 01: 00.1 Dispositivo de áudio: Controlador de áudio de alta definição NVIDIA Corporation (rev a1) 02: 00.0 Controlador de rede: Ralink corp. RT3090 Controlador Ethernet 802.11n 1T / 1R PCIe 03: 00.0 Ethernet: Realtek Semiconductor Co., Ltd. RTL8111 / 8168/8411 Controlador Ethernet Gigabit PCI Express (rev 06) 3f: 00.0 Ponte do host: Intel Corporation Core Processor Core QuickPath Architecture Genérico não- registradores principais (rev 02) 3f: 00.1 Bridge host: decodificador de endereços do sistema de arquitetura do processador central Intel Corporation QuickPath (rev 02) 3f: 02.0 Bridge host: processador Intel Corporation QPI Link 0 (rev 02) 3f: 02.1 Ponte do host: Intel Corporation 1ª geração do processador Core i3 / 5/7 QPI físico 0 (rev 02) 3f: 02.2 Ponte do host: Intel Corporation 1ª geração do processador Core i3 / 5/7 reservado (rev 02) 3f: 02.3 host bridge: Processador Intel Corporation de primeira geração Core i3 / 5/7 reservado (rev 02) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883780/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1869465] Re: Kdump-Tools: Makedumpfile Failed, Falling Back To 'Cp'
The autopkgtests regressions are unrelated to this SRU. Sure enough: the patch is for arm64 only, but the archs failing are i386, ppc64el, and s390x. The "regressions" also happen with the version in -updates, in the same way as in -proposed. makedumpfile [eoan/i386] [1] Version TriggersDateDurationRequester Result 1:1.6.6-2ubuntu2... 2020-06-16 19:07:17 UTC 0h 05m 47s mfo faillog artifacts ♻ 1:1.6.6-2ubuntu2.1 ... 2020-06-16 11:51:34 UTC 0h 07m 23s mfo faillog artifacts ♻ makedumpfile [eoan/ppc64el] [2] Version TriggersDateDurationRequester Result 1:1.6.6-2ubuntu2... 2020-06-16 18:56:11 UTC 0h 06m 31s mfo faillog artifacts ♻ 1:1.6.6-2ubuntu2.1 ... 2020-06-16 11:47:27 UTC 0h 05m 22s mfo faillog artifacts ♻ makedumpfile [bionic/s390x] [3] Version TriggersDateDurationRequester Result 1:1.6.5-1ubuntu1~18.04.4... 2020-06-16 18:52:05 UTC 0h 03m 08s mfo faillog artifacts ♻ 1:1.6.5-1ubuntu1~18.04.5... 2020-06-16 11:46:00 UTC 0h 03m 06s mfo faillog artifacts ♻ [1] https://autopkgtest.ubuntu.com/packages/m/makedumpfile/eoan/i386 [2] https://autopkgtest.ubuntu.com/packages/m/makedumpfile/eoan/ppc64el [3] https://autopkgtest.ubuntu.com/packages/m/makedumpfile/bionic/s390x -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1869465 Title: Kdump-Tools: Makedumpfile Failed, Falling Back To 'Cp' Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: Fix Committed Status in makedumpfile source package in Bionic: Fix Committed Status in makedumpfile source package in Eoan: Fix Committed Status in makedumpfile source package in Focal: Fix Committed Status in makedumpfile source package in Groovy: Fix Released Status in makedumpfile package in Debian: New Bug description: [Impact] On some arm systems makedumpfile fails to translate virtual to physical addresses properly. This may result in makedumpfile looping forever exhausting all memory, or translating a virtual address to an invalid physical address and then failing and falling back to cp. The reason it cannot resolve some addresses is because the PMD mask is wrong. When physical address mask allows up to 48bits pmd mask should allow the same, currently pmd mask is set to 40bits (see commit [1]). Commit [1] fixes this bug. [Test Case] To hit this bug you need a system that needs physical addresses over 1TB. This may be either because you have a lot of memory or because the firmware mapped some memory above 1TB for some reason [1]. A user hit this bug because firmware mapped memory above 1TB and provided a dump so I could reproduce the bug when running makedumpfile on the dump. [Regression Potential] This commit changes the PMD_SECTION_MASK for arm64. So any regression potential would only affect arm64 systems. In addition PMD_SECTION_MASK is used in translation from virtual to physical addresses and therefore any regression would happen during this process. [Other] [1] https://github.com/makedumpfile/makedumpfile/commit/7242ae4cb5288df626f464ced0a8b60fd669100b When testing kdump on Ubuntu 18.04.4 (arm64) GA kernel, makedumpfile fails. The test steps are as follows: # echo 1> / proc / sys / kernel / sysrq # echo c> / proc / sysrq-trigger The logs are as follows: kdump-tools[646]: starting kdump-tools: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/202003251128/dump-incomplete kdump-tools[646]: readpage_elf: Attempt to read non-existent page at 0x0 kdump-tools[646]: readmem: type_addr: 1, addr:ff0, size:8 kdump-tools[646]: vaddr_to_paddr_arm64: Can't read pud kdump-tools[646]: readmem: Can't convert a virtual address(9e653690) to physical address. kdump-tools[646]: readmem: type_addr: 0, addr:9e653690, size:1032 kdump-tools[646]: validate_mem_section: Can't read mem_section array. kdump-tools[646]: get_mem_section: Could not validate mem_section. kdump-tools[646]: get_mm_sparsemem: Can't get the address of mem_section. kdump-tools[646]: makedumpfile Failed. kdump-tools[646]: * kdump-tools: makedumpfile failed, falling back to 'cp' But when I use the HWE kernel, I find that there is no such problem. The HEW kernel version: 5.3.0-42-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1869465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpa
[Kernel-packages] [Bug 1883780] Re: Problems with module rt2800 and falling connection
** Description changed: - With kernel: 5.4.0.37 - Gnome: 3.36 - Version: 20.04 LTS + Com o kernel: 5.4.0.37 + Gnome: 3.36 + Versão: 20.04 LTS Network Manager: 1.22.10 - The configuration that I tried em rt2800pci.conf em /etc/modprobe.d/ - options rt2800pci nohwcrypt=1 - Not solved + A configuração que eu tentei em rt2800pci.conf em /etc/modprobe.d/ + options rt2800pci nohwcrypt = 1 + Não resolvido - My suspicion that this module is causing the machine to overheat, - because if I run modprobe -r rt2800pci the machine does not overheat as - much as when I load this module. + Connect for a period and then disconnect. Leaving the connection + unstable. - Frequent drops of connection occur and sometimes it doesn't even work. + Suspeito que este módulo esteja causando superaquecimento na máquina, + porque se eu executar o modprobe -r rt2800pci, a máquina não + superaquecerá tanto quanto quando carrego este módulo. - I WANT TO EMPHASIZE THAT THIS ONLY OCCURS WITH UBUNTU, OTHER - DISTRIBUTIONS THAT USE THIS KERNEL DOES NOT OCCUR THESE CONNECTION FALLS - I AM REPORTING. + Quedas freqüentes de conexão ocorrem e, às vezes, nem funcionam. - 00:00.0 Host bridge: Intel Corporation Core Processor DRAM Controller (rev 02) - 00:01.0 PCI bridge: Intel Corporation Core Processor PCI Express x16 Root Port (rev 02) - 00:16.0 Communication controller: Intel Corporation 5 Series/3400 Series Chipset HECI Controller (rev 06) - 00:1a.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05) - 00:1b.0 Audio device: Intel Corporation 5 Series/3400 Series Chipset High Definition Audio (rev 05) - 00:1c.0 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1 (rev 05) - 00:1c.1 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 2 (rev 05) - 00:1c.4 PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 5 (rev 05) - 00:1d.0 USB controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller (rev 05) - 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev a5) - 00:1f.0 ISA bridge: Intel Corporation HM55 Chipset LPC Interface Controller (rev 05) - 00:1f.2 SATA controller: Intel Corporation 5 Series/3400 Series Chipset 4 port SATA AHCI Controller (rev 05) - 00:1f.3 SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller (rev 05) - 00:1f.6 Signal processing controller: Intel Corporation 5 Series/3400 Series Chipset Thermal Subsystem (rev 05) - 01:00.0 VGA compatible controller: NVIDIA Corporation GT218M [GeForce 310M] (rev a2) - 01:00.1 Audio device: NVIDIA Corporation High Definition Audio Controller (rev a1) - 02:00.0 Network controller: Ralink corp. RT3090 Wireless 802.11n 1T/1R PCIe - 03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06) - 3f:00.0 Host bridge: Intel Corporation Core Processor QuickPath Architecture Generic Non-core Registers (rev 02) - 3f:00.1 Host bridge: Intel Corporation Core Processor QuickPath Architecture System Address Decoder (rev 02) - 3f:02.0 Host bridge: Intel Corporation Core Processor QPI Link 0 (rev 02) - 3f:02.1 Host bridge: Intel Corporation 1st Generation Core i3/5/7 Processor QPI Physical 0 (rev 02) - 3f:02.2 Host bridge: Intel Corporation 1st Generation Core i3/5/7 Processor Reserved (rev 02) - 3f:02.3 Host bridge: Intel Corporation 1st Generation Core i3/5/7 Processor Reserved (rev 02) + QUERO DESTACAR QUE ISSO SÓ OCORRE COM A UBUNTU, OUTRAS DISTRIBUIÇÕES QUE + USAM ESTE KERNEL NÃO OCORREM ESTAS QUEDAS DE CONEXÃO QUE ESTOU + RELATANDO. + + 00: 00.0 Ponte host: Controladora DRAM do processador principal Intel Corporation (rev 02) + 00: 01.0 Ponte PCI: Processador principal Intel Corporation Porta raiz PCI Express x16 (rev 02) + 00: 16.0 Controlador de comunicação: Intel Corporation série 5/3400 chipset HECI Controlador (rev 06) + 00: 1a.0 Controlador USB: chipset Intel Corporation série 5/3400 Series Controlador host USB2 aprimorado (rev 05) + 00: 1b.0 Dispositivo de áudio: Áudio Intel de alta definição Chipset série 5 da série Intel / 3400 (rev 05) + Ponte PCI 00: 1c.0: Porta raiz 1 do PCI Express Intel Chipset série 5/3400 Series (rev 05) + Ponte PCI 00: 1c.1: Porta raiz 2 do chipset Intel Corporation série 5/3400 (rev) 05) + 00: 1c.4 Ponte PCI: Intel Corporation Série 5/3400 Chipset PCI Express Root Port 5 (rev 05) + 00: 1d.0 Controlador USB: Intel Corporation série 5/3400 Series Chipset Controlador host avançado USB2 (rev 05) + 00 : 1e.0 ponte PCI: Intel Corporation 82801 Mobile PCI Bridge (rev a5) + 00: 1f.0 ponte ISA: Intel Corporation HM55 Chipset LPC Interface Controller (rev 05) + 00: 1f.2 SATA controller: Intel Corporation 5 Series / 3400 Controlador SATA AHCI da porta 4 do chipset série 4 (rev 05) + 00: 1f.3 SMBus: Intel Corporation Série 5/3400 Controlador SMBus do chipset
[Kernel-packages] [Bug 1869465] Re: Kdump-Tools: Makedumpfile Failed, Falling Back To 'Cp'
Also, ppc64/s390 are being tracked here: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1851663 It's a common issue, and difficult to debug (if we run tests locally, we can't reproduce and they succeeed). Regarding i386, we should remove tests for i386 in Eoan and Focal. Cheers, Guilherme -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1869465 Title: Kdump-Tools: Makedumpfile Failed, Falling Back To 'Cp' Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: Fix Committed Status in makedumpfile source package in Bionic: Fix Committed Status in makedumpfile source package in Eoan: Fix Committed Status in makedumpfile source package in Focal: Fix Committed Status in makedumpfile source package in Groovy: Fix Released Status in makedumpfile package in Debian: New Bug description: [Impact] On some arm systems makedumpfile fails to translate virtual to physical addresses properly. This may result in makedumpfile looping forever exhausting all memory, or translating a virtual address to an invalid physical address and then failing and falling back to cp. The reason it cannot resolve some addresses is because the PMD mask is wrong. When physical address mask allows up to 48bits pmd mask should allow the same, currently pmd mask is set to 40bits (see commit [1]). Commit [1] fixes this bug. [Test Case] To hit this bug you need a system that needs physical addresses over 1TB. This may be either because you have a lot of memory or because the firmware mapped some memory above 1TB for some reason [1]. A user hit this bug because firmware mapped memory above 1TB and provided a dump so I could reproduce the bug when running makedumpfile on the dump. [Regression Potential] This commit changes the PMD_SECTION_MASK for arm64. So any regression potential would only affect arm64 systems. In addition PMD_SECTION_MASK is used in translation from virtual to physical addresses and therefore any regression would happen during this process. [Other] [1] https://github.com/makedumpfile/makedumpfile/commit/7242ae4cb5288df626f464ced0a8b60fd669100b When testing kdump on Ubuntu 18.04.4 (arm64) GA kernel, makedumpfile fails. The test steps are as follows: # echo 1> / proc / sys / kernel / sysrq # echo c> / proc / sysrq-trigger The logs are as follows: kdump-tools[646]: starting kdump-tools: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/202003251128/dump-incomplete kdump-tools[646]: readpage_elf: Attempt to read non-existent page at 0x0 kdump-tools[646]: readmem: type_addr: 1, addr:ff0, size:8 kdump-tools[646]: vaddr_to_paddr_arm64: Can't read pud kdump-tools[646]: readmem: Can't convert a virtual address(9e653690) to physical address. kdump-tools[646]: readmem: type_addr: 0, addr:9e653690, size:1032 kdump-tools[646]: validate_mem_section: Can't read mem_section array. kdump-tools[646]: get_mem_section: Could not validate mem_section. kdump-tools[646]: get_mm_sparsemem: Can't get the address of mem_section. kdump-tools[646]: makedumpfile Failed. kdump-tools[646]: * kdump-tools: makedumpfile failed, falling back to 'cp' But when I use the HWE kernel, I find that there is no such problem. The HEW kernel version: 5.3.0-42-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1869465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883597] Re: Kernel 4.4.0-184 hangs when issuing tc qdisc command
I can confirm this happens whenever sch_fq is used, regardless of the
hardware/driver. This seems to be caused by kernel 4.4.0-180 adding a
backport of upstream commit:
695b4ec0f0a9 ("pkt_sched: fq: use proper locking in fq_dump_stats()")
This commit was pulled in as part of upstream stable 4.4.223. I believe
backporting this commit to stable was a mistake, and that it should just
be reverted. I've reported this to upstream as well, which should appear
here once Lore syncs up:
https://lore.kernel.org/netdev/874krazvdf@toke.dk/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1883597
Title:
Kernel 4.4.0-184 hangs when issuing tc qdisc command
Status in linux package in Ubuntu:
Confirmed
Bug description:
On stock kernel 4.4.0.184-214, issuing "tc qdisc add dev eth0 root fq maxrate
25mbit" causes CPU lockup
(NMI watchdog: BUG: soft lockup - CPU#26 stuck for 22s! [tc:6394])
This does not occur on 4.4.0.179 or earlier.
Happens on both a intel i40e driver and ixgbe.
---
AlsaDevices:
total 0
crw-rw+ 1 root audio 116, 1 Jun 15 14:52 seq
crw-rw+ 1 root audio 116, 33 Jun 15 14:52 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.20.1-0ubuntu2.23
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=09e7e0db-e2ed-4cb1-8d1b-2eefdaa81d3a
InstallationDate: Installed on 2019-02-22 (479 days ago)
InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64
(20170801)
IwConfig: Error: [Errno 2] No such file or directory
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd
Bus 001 Device 003: ID 0557:7000 ATEN International Co., Ltd Hub
Bus 001 Device 002: ID 0d3d:0040 Tangtop Technology Co., Ltd PS/2 Adapter
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Supermicro SSG-6029P-E1CR12L
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US
SHELL=/bin/bash
ProcFB: 0 EFI VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-184-generic
root=UUID=8b0d6ed1-2955-4f7a-aeb6-cbfa319aed17 ro text nomodeset consoleblank=0
nopti crashkernel=384M-:128M crashkernel=384M-2G:64M,2G-:768M
ProcVersionSignature: Ubuntu 4.4.0-184.214-generic 4.4.223
RelatedPackageVersions:
linux-restricted-modules-4.4.0-184-generic N/A
linux-backports-modules-4.4.0-184-generic N/A
linux-firmware 1.157.23
RfKill: Error: [Errno 2] No such file or directory
Tags: xenial
Uname: Linux 4.4.0-184-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
_MarkForUpload: True
dmi.bios.date: 02/27/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2.0b
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: X11DPH-T
dmi.board.vendor: Supermicro
dmi.board.version: 1.01
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 1
dmi.chassis.vendor: Supermicro
dmi.chassis.version: 0123456789
dmi.modalias:
dmi:bvnAmericanMegatrendsInc.:bvr2.0b:bd02/27/2018:svnSupermicro:pnSSG-6029P-E1CR12L:pvr0123456789:rvnSupermicro:rnX11DPH-T:rvr1.01:cvnSupermicro:ct1:cvr0123456789:
dmi.product.name: SSG-6029P-E1CR12L
dmi.product.version: 0123456789
dmi.sys.vendor: Supermicro
---
AlsaDevices:
total 0
crw-rw+ 1 root audio 116, 1 Jun 15 14:52 seq
crw-rw+ 1 root audio 116, 33 Jun 15 14:52 timer
AplayDevices: Error: [Errno 2] No such file or directory
ApportVersion: 2.20.1-0ubuntu2.23
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
DistroRelease: Ubuntu 16.04
HibernationDevice: RESUME=UUID=09e7e0db-e2ed-4cb1-8d1b-2eefdaa81d3a
InstallationDate: Installed on 2019-02-22 (479 days ago)
InstallationMedia: Ubuntu-Server 16.04.3 LTS "Xenial Xerus" - Release amd64
(20170801)
IwConfig: Error: [Errno 2] No such file or directory
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 0557:2419 ATEN International Co., Ltd
Bus 001 Device 003: ID 0557:7000 ATEN International Co., Ltd Hub
Bus 001 Device 002: ID 0d3d:0040 Tangtop Technology Co., Ltd PS/2 Adapter
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Supermicro SSG-6029P-E1CR12L
Package: linux (not installed)
PciMultimedia:
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=en_US
SHELL=/bin/bash
ProcFB: 0 EFI V
[Kernel-packages] [Bug 1869465] Re: Kdump-Tools: Makedumpfile Failed, Falling Back To 'Cp'
Hey Guilherme, Thanks for the pointers and confirming these are not regressions, but known issues. :) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1869465 Title: Kdump-Tools: Makedumpfile Failed, Falling Back To 'Cp' Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: Fix Committed Status in makedumpfile source package in Bionic: Fix Committed Status in makedumpfile source package in Eoan: Fix Committed Status in makedumpfile source package in Focal: Fix Committed Status in makedumpfile source package in Groovy: Fix Released Status in makedumpfile package in Debian: New Bug description: [Impact] On some arm systems makedumpfile fails to translate virtual to physical addresses properly. This may result in makedumpfile looping forever exhausting all memory, or translating a virtual address to an invalid physical address and then failing and falling back to cp. The reason it cannot resolve some addresses is because the PMD mask is wrong. When physical address mask allows up to 48bits pmd mask should allow the same, currently pmd mask is set to 40bits (see commit [1]). Commit [1] fixes this bug. [Test Case] To hit this bug you need a system that needs physical addresses over 1TB. This may be either because you have a lot of memory or because the firmware mapped some memory above 1TB for some reason [1]. A user hit this bug because firmware mapped memory above 1TB and provided a dump so I could reproduce the bug when running makedumpfile on the dump. [Regression Potential] This commit changes the PMD_SECTION_MASK for arm64. So any regression potential would only affect arm64 systems. In addition PMD_SECTION_MASK is used in translation from virtual to physical addresses and therefore any regression would happen during this process. [Other] [1] https://github.com/makedumpfile/makedumpfile/commit/7242ae4cb5288df626f464ced0a8b60fd669100b When testing kdump on Ubuntu 18.04.4 (arm64) GA kernel, makedumpfile fails. The test steps are as follows: # echo 1> / proc / sys / kernel / sysrq # echo c> / proc / sysrq-trigger The logs are as follows: kdump-tools[646]: starting kdump-tools: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/202003251128/dump-incomplete kdump-tools[646]: readpage_elf: Attempt to read non-existent page at 0x0 kdump-tools[646]: readmem: type_addr: 1, addr:ff0, size:8 kdump-tools[646]: vaddr_to_paddr_arm64: Can't read pud kdump-tools[646]: readmem: Can't convert a virtual address(9e653690) to physical address. kdump-tools[646]: readmem: type_addr: 0, addr:9e653690, size:1032 kdump-tools[646]: validate_mem_section: Can't read mem_section array. kdump-tools[646]: get_mem_section: Could not validate mem_section. kdump-tools[646]: get_mm_sparsemem: Can't get the address of mem_section. kdump-tools[646]: makedumpfile Failed. kdump-tools[646]: * kdump-tools: makedumpfile failed, falling back to 'cp' But when I use the HWE kernel, I find that there is no such problem. The HEW kernel version: 5.3.0-42-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1869465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1879082] Re: Kernel reporting 100% battery, always
#17 looks like correct behavours. I also noticed #13 said battery was acting without problems anymore. Is it still the case or did you have problems when running #17? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1879082 Title: Kernel reporting 100% battery, always Status in linux package in Ubuntu: In Progress Bug description: Running Kubuntu 20.04: Regardless of whether the laptop is plugged- in, or the battery state (Even just before dying) the reported percentage is incorrect and the system believes it is plugged in at all times (see upower -d below, it is always the same). $ cat /proc/version_signature Ubuntu 5.4.0-29.33-generic 5.4.30 $ lsb_release -a LSB Version: core-11.1.0ubuntu2-noarch:printing-11.1.0ubuntu2-noarch:security-11.1.0ubuntu2-noarch Distributor ID: Ubuntu Description:Ubuntu 20.04 LTS Release:20.04 Codename: focal $ uname -a Linux Vergil 5.4.0-29-generic #33-Ubuntu SMP Wed Apr 29 14:32:27 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux $ upower -d Device: /org/freedesktop/UPower/devices/line_power_ACAD native-path: ACAD power supply: yes updated: Sat 16 May 2020 12:35:46 PM CDT (909 seconds ago) has history: no has statistics: no line-power warning-level: none online: yes icon-name: 'ac-adapter-symbolic' Device: /org/freedesktop/UPower/devices/battery_BAT1 native-path: BAT1 vendor: TOSHIBA model:PABAS0241231 serial: power supply: yes updated: Sat 16 May 2020 12:49:47 PM CDT (68 seconds ago) has history: yes has statistics: yes battery present: yes rechargeable:yes state: fully-charged warning-level: none energy: 4294.84 Wh energy-empty:0 Wh energy-full: 4294.84 Wh energy-full-design: 4294.84 Wh energy-rate: 0 W voltage: 65.535 V percentage: 100% capacity:100% technology: lithium-ion icon-name: 'battery-full-charged-symbolic' Device: /org/freedesktop/UPower/devices/DisplayDevice power supply: yes updated: Sat 16 May 2020 12:32:09 PM CDT (1126 seconds ago) has history: no has statistics: no battery present: yes state: fully-charged warning-level: none energy: 4294.84 Wh energy-full: 4294.84 Wh energy-rate: 0 W percentage: 100% icon-name: 'battery-full-charged-symbolic' Daemon: daemon-version: 0.99.11 on-battery: no lid-is-closed: no lid-is-present: yes critical-action: HybridSleep ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: sperger1191 F pulseaudio /dev/snd/controlC0: sperger1191 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat May 16 12:41:59 2020 InstallationDate: Installed on 2020-03-11 (65 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: TOSHIBA Satellite C55-B ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=fd25621b-6551-420a-a1c5-13a0746ae679 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-10 (5 days ago) dmi.bios.date: 07/19/2014 dmi.bios.vendor: TOSHIBA dmi.bios.version: 1.30 dmi.board.asset.tag: * dmi.board.name: ZSWAA dmi.board.vendor: TOSHIBA dmi.board.version: 1.00 dmi.chassis.asset.tag: * dmi.chassis.type: 10 dmi.chassis.vendor: TOSHIBA dmi.chassis.version: * dmi.modalias: dmi:bvnTOSHIBA:bvr1.30:bd07/19/2014:svnTOSHIBA:pnSatelliteC55-B:pvrPSCLUU-05M07V:rvnTOSHIBA:rnZSWAA:rvr1.00:cvnTOSHIBA:ct10:cvr*: dmi.product.family: * dmi.product.name: Satellite C55-B dmi.product.sku: PSCLUU dmi.product.version: PSCLUU-05M07V dmi.sys.vendor: TOSHIBA To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1879082/+subscriptions --
[Kernel-packages] [Bug 1869465] Re: Kdump-Tools: Makedumpfile Failed, Falling Back To 'Cp'
You're very welcome mfo, thanks for following this SRU in order to get that released soon =) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1869465 Title: Kdump-Tools: Makedumpfile Failed, Falling Back To 'Cp' Status in makedumpfile package in Ubuntu: Fix Released Status in makedumpfile source package in Xenial: Fix Committed Status in makedumpfile source package in Bionic: Fix Committed Status in makedumpfile source package in Eoan: Fix Committed Status in makedumpfile source package in Focal: Fix Committed Status in makedumpfile source package in Groovy: Fix Released Status in makedumpfile package in Debian: New Bug description: [Impact] On some arm systems makedumpfile fails to translate virtual to physical addresses properly. This may result in makedumpfile looping forever exhausting all memory, or translating a virtual address to an invalid physical address and then failing and falling back to cp. The reason it cannot resolve some addresses is because the PMD mask is wrong. When physical address mask allows up to 48bits pmd mask should allow the same, currently pmd mask is set to 40bits (see commit [1]). Commit [1] fixes this bug. [Test Case] To hit this bug you need a system that needs physical addresses over 1TB. This may be either because you have a lot of memory or because the firmware mapped some memory above 1TB for some reason [1]. A user hit this bug because firmware mapped memory above 1TB and provided a dump so I could reproduce the bug when running makedumpfile on the dump. [Regression Potential] This commit changes the PMD_SECTION_MASK for arm64. So any regression potential would only affect arm64 systems. In addition PMD_SECTION_MASK is used in translation from virtual to physical addresses and therefore any regression would happen during this process. [Other] [1] https://github.com/makedumpfile/makedumpfile/commit/7242ae4cb5288df626f464ced0a8b60fd669100b When testing kdump on Ubuntu 18.04.4 (arm64) GA kernel, makedumpfile fails. The test steps are as follows: # echo 1> / proc / sys / kernel / sysrq # echo c> / proc / sysrq-trigger The logs are as follows: kdump-tools[646]: starting kdump-tools: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/202003251128/dump-incomplete kdump-tools[646]: readpage_elf: Attempt to read non-existent page at 0x0 kdump-tools[646]: readmem: type_addr: 1, addr:ff0, size:8 kdump-tools[646]: vaddr_to_paddr_arm64: Can't read pud kdump-tools[646]: readmem: Can't convert a virtual address(9e653690) to physical address. kdump-tools[646]: readmem: type_addr: 0, addr:9e653690, size:1032 kdump-tools[646]: validate_mem_section: Can't read mem_section array. kdump-tools[646]: get_mem_section: Could not validate mem_section. kdump-tools[646]: get_mm_sparsemem: Can't get the address of mem_section. kdump-tools[646]: makedumpfile Failed. kdump-tools[646]: * kdump-tools: makedumpfile failed, falling back to 'cp' But when I use the HWE kernel, I find that there is no such problem. The HEW kernel version: 5.3.0-42-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1869465/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1657367] Re: Intel-based ethernet interfaces can't detect link state
I'm having this issue in a fresh install of Ubuntu 20.04 with an Intel NIC and the IGC driver. https://askubuntu.com/questions/1244745/ubuntu-20-04-intel-network- connectivity-issue-bug-in-igc Should I submit new logfiles? Start a new bug? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1657367 Title: Intel-based ethernet interfaces can't detect link state Status in linux package in Ubuntu: Confirmed Bug description: I have number of SUN x86-based servers with Intel Ethenet controllers. Both igb and e1000 drivers are used. All servers have strange issue: after fresh Ubuntu 16.04 installation all ethernet links are in down state even if cables are plugged in. At the network switch side links are in up state! If i try to manually up the link via ip link tool, all works fine. When i try to manually assign an IP address to "dead" interface it brings up... After reboot all links are down again. Any suggestion? Environment: DISTRIB_ID=Ubuntu DISTRIB_RELEASE=16.04 DISTRIB_CODENAME=xenial DISTRIB_DESCRIPTION="Ubuntu 16.04.1 LTS" NAME="Ubuntu" VERSION="16.04.1 LTS (Xenial Xerus)" Description of affected adapters: 10:00.1 Ethernet controller: Intel Corporation 82571EB Gigabit Ethernet Controller (rev 06) Subsystem: QLogic Corp. 82571EB Gigabit Ethernet Controller Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: e1000e Kernel modules: e1000e 1f:00.0 Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01) Subsystem: Oracle/SUN 82576 Gigabit Network Connection Physical Slot: 0 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Kernel driver in use: igb Kernel modules: igb Modules: modinfo igb filename: /lib/modules/4.4.0-59-generic/kernel/drivers/net/ethernet/intel/igb/igb.ko version:5.3.0-k modinfo e1000e filename: /lib/modules/4.4.0-59-generic/kernel/drivers/net/ethernet/intel/e1000e/e1000e.ko version:3.2.6-k --- AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Jan 17 10:38 seq crw-rw+ 1 root audio 116, 33 Jan 17 10:38 timer AplayDevices: Error: [Errno 2] No such file or directory ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=a4e3c371-9e25-45f8-ae21-6e876f19c276 InstallationDate: Installed on 2016-12-29 (19 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) IwConfig: Error: [Errno 2] No such file or directory MachineType: Oracle Corporation SUN BLADE X6270 M2 SERVER MODULE NonfreeKernelModules: zfs zunicode zcommon znvpair zavl Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-59-generic root=UUID=396b00e0-4d6d-4143-a0a0-d954eafc3c12 ro ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 RelatedPackageVersions: linux-restricted-modules-4.4.0-59-generic N/A linux-backports-modules-4.4.0-59-generic N/A linux-firmware1.157.6 RfKill: Error: [Errno 2] No such file or directory Tags: xenial Uname: Linux 4.4.0-59-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 02/17/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 08070400 dmi.board.asset.tag: 511-1418-03 dmi.board.name: ASSY,BLADE,X6270,M2 dmi.board.vendor: Oracle Corporation dmi.board.version: 511-1418-03 dmi.chassis.type: 28 dmi.chassis.vendor: ORACLE CORPORATION dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr08070400:bd02/17/2014:svnOracleCorporation:pnSUNBLADEX6270M2SERVERMODULE:pvr:rvnOracleCorporation:rnASSY,BLADE,X6270,M2:rvr511-1418-03:cvnORACLECORPORATION:ct28:cvr: dmi.product.name: SUN BLADE X6270 M2 SERVER MODULE dmi.sys.vendor: Oracle Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1657367/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877955] Comment bridged from LTC Bugzilla
--- Comment From naynj...@ibm.com 2020-06-16 17:36 EDT---
Thanks. I have PPA keys as those versions we tested last time.
I do not have common or standard key. Can you please share the tar or path for
that ?
Thanks & Regards,
- Nayna
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1877955
Title:
Fix for secure boot rules in IMA arch policy on powerpc
Status in The Ubuntu-power-systems project:
Fix Committed
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Groovy:
In Progress
Bug description:
SRU Justification:
==
[Impact]
* Currently the kernel module appended signature is verified twice
(finit_module) - once by the module_sig_check() and again by IMA.
* To prevent this the powerpc secure boot rules define an IMA
architecture specific policy rule only if CONFIG_MODULE_SIG_FORCE is
not enabled.
* But this doesn't take the ability into account of enabling
"sig_enforce" at the boot command line (module.sig_enforce=1).
* Including the IMA module appraise rule results in failing the
finit_module syscall, unless the module signing public key is loaded
onto the IMA keyring.
* This patch fixes secure boot policy rules to be based on
CONFIG_MODULE_SIG instead.
[Fix]
* fa4f3f56ccd28ac031ab275e673ed4098855fed4 fa4f3f56ccd2 "powerpc/ima:
Fix secure boot rules in ima arch policy"
[Test Case]
* Perform a secure boot on a powerpc system with
'module.sig_enforce=1' set at the boot command.
* If the IMA module appraise rule is included, the finit_module
syscall will fail (unless the module signing public key got loaded
onto the IMA keyring) without having the patch in place.
* The verification needs to be done by the IBM Power team.
[Regression Potential]
* There is (always) a certain regression risk with having code
changes, especially in the secure boot area.
* But this patch is limited to the powerpc platform and will not
affect any other architecture.
* It got discussed at
https://lore.kernel.org/r/1588342612-14532-1-git-send-email-na...@linux.ibm.com
before it became finally upstream accepted with kernel 5.7-rc7.
* The secure boot code itself wasn't really touched, rather than it's basis
for execution.
The IMA policy rule for module appraisal is now added only if
'CONFIG_MODULE_SIG' is not enabled (instead of CONFIG_MODULE_SIG_FORCE).
Hence the change is very limited and straightforward.
[Other]
* Since the patch got upstream with 5.7-rc7, it is already in groovy, hence
this SRU is for focal only.
__
== Comment: #0 - Michael Ranweiler - 2020-04-22
14:44:31 ==
+++ This bug was initially created as a clone of Bug #184073 +++
This bug is a follow on to LP 1866909 to address a missing piece -
only half the following patch was included in 5.4.0-24.28.
The upstream patch has an additional fix but it?s not critical for GA.
It can get included as part of bug fixes. It also affects only power.
The patch("powerpc/ima: fix secure boot rules in ima arch policy") is
posted to linux-integrity and linuxppc-dev mailing list
(https://lore.kernel.org/linux-integrity/1586549618-6106-1-git-send-
email-na...@linux.ibm.com/T/#u)
If there are any issues identified during further testing, they will
get opened as separate issue to be addressed later.
Thanks & Regards,
- Nayna
== Comment: #4 - Michael Ranweiler - 2020-05-11
02:23:35 ==
Updated posting:
https://lore.kernel.org/linux-integrity/1588342612-14532-1-git-send-
email-na...@linux.ibm.com/T/#u
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1877955/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877955] Comment bridged from LTC Bugzilla
--- Comment From naynj...@ibm.com 2020-06-16 17:51 EDT---
To be specific.
sudo apt-key list
shows:
ubuntu@ltc-wspoon13:/$ apt-key list
/etc/apt/trusted.gpg.d/canonical-kernel-team_ubuntu_bootstrap.gpg
-
pub rsa1024 2010-12-01 [SC]
110E 21D8 B0E2 A1F0 243A F682 0856 F197 B892 ACEA
uid [ unknown] Launchpad PPA for Canonical Kernel Team
/etc/apt/trusted.gpg.d/sforshee_ubuntu_lp1866909.gpg
pub rsa1024 2011-10-06 [SC]
6B5B 9C22 2E05 413A F654 1676 1212 D9F6 559B 2FA8
uid [ unknown] Launchpad PPA for Seth Forshee
/etc/apt/trusted.gpg.d/ubuntu-keyring-2012-archive.gpg
--
pub rsa4096 2012-05-11 [SC]
790B C727 7767 219C 42C8 6F93 3B4F E6AC C0B2 1F32
uid [ unknown] Ubuntu Archive Automatic Signing Key (2012)
/etc/apt/trusted.gpg.d/ubuntu-keyring-2012-cdimage.gpg
--
pub rsa4096 2012-05-11 [SC]
8439 38DF 228D 22F7 B374 2BC0 D94A A3F0 EFE2 1092
uid [ unknown] Ubuntu CD Image Automatic Signing Key (2012)
/etc/apt/trusted.gpg.d/ubuntu-keyring-2018-archive.gpg
--
pub rsa4096 2018-09-17 [SC]
F6EC B376 2474 EDA9 D21B 7022 8719 20D1 991B C93C
uid [ unknown] Ubuntu Archive Automatic Signing Key (2018)
I need OPAL signing key as in path -
ppa.launchpad.net/sforshee/lp1866909/ubuntu/dists/focal/main/signed
/linux-ppc64el/current/signed.tar.gz
If you will extract this, there is one opal.x509 which is used to sign
the kernel. This one is for PPA kernel if I am not missing something.
And that is the key I need for proposed. So, if you can share the common
or standard OPAL signing key which I can use for proposed, it would be
helpful.
Thanks & Regards,
- Nayna
Thanks & Regards,
- Nayna
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1877955
Title:
Fix for secure boot rules in IMA arch policy on powerpc
Status in The Ubuntu-power-systems project:
Fix Committed
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Groovy:
In Progress
Bug description:
SRU Justification:
==
[Impact]
* Currently the kernel module appended signature is verified twice
(finit_module) - once by the module_sig_check() and again by IMA.
* To prevent this the powerpc secure boot rules define an IMA
architecture specific policy rule only if CONFIG_MODULE_SIG_FORCE is
not enabled.
* But this doesn't take the ability into account of enabling
"sig_enforce" at the boot command line (module.sig_enforce=1).
* Including the IMA module appraise rule results in failing the
finit_module syscall, unless the module signing public key is loaded
onto the IMA keyring.
* This patch fixes secure boot policy rules to be based on
CONFIG_MODULE_SIG instead.
[Fix]
* fa4f3f56ccd28ac031ab275e673ed4098855fed4 fa4f3f56ccd2 "powerpc/ima:
Fix secure boot rules in ima arch policy"
[Test Case]
* Perform a secure boot on a powerpc system with
'module.sig_enforce=1' set at the boot command.
* If the IMA module appraise rule is included, the finit_module
syscall will fail (unless the module signing public key got loaded
onto the IMA keyring) without having the patch in place.
* The verification needs to be done by the IBM Power team.
[Regression Potential]
* There is (always) a certain regression risk with having code
changes, especially in the secure boot area.
* But this patch is limited to the powerpc platform and will not
affect any other architecture.
* It got discussed at
https://lore.kernel.org/r/1588342612-14532-1-git-send-email-na...@linux.ibm.com
before it became finally upstream accepted with kernel 5.7-rc7.
* The secure boot code itself wasn't really touched, rather than it's basis
for execution.
The IMA policy rule for module appraisal is now added only if
'CONFIG_MODULE_SIG' is not enabled (instead of CONFIG_MODULE_SIG_FORCE).
Hence the change is very limited and straightforward.
[Other]
* Since the patch got upstream with 5.7-rc7, it is already in groovy, hence
this SRU is for focal only.
__
== Comment: #0 - Michael Ranweiler - 2020-04-22
14:44:31 ==
+++ This bug was initially created as a clone of Bug #184073 +++
This bug is a follow on to LP 1866909 to address a missing piece -
only half the following patch was included in 5.4.0-24.28.
The upstream patch has an additional fix but it?s not critical for GA.
It can get included as part of bug fixes. It also affects only power.
The patch("powerpc/ima: fix secure boot rules in ima arch policy") is
posted to linux-integrity and linux
[Kernel-packages] [Bug 1877955] Re: Fix for secure boot rules in IMA arch policy on powerpc
Hi,
Each signed object is published on in the repository under
/$suite/main/signed/$src-$arch. I.e. the linux in focal proposed signed
artefacts can be found at:
http://ports.ubuntu.com/dists/focal-proposed/main/signed/linux-ppc64el/
I.e. http://ports.ubuntu.com/dists/focal-proposed/main/signed/linux-
ppc64el/5.4.0-38.42/signed.tar.gz
inside that tarball, there should be $version/control/opal.x509 public
certificate that is used for signing.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1877955
Title:
Fix for secure boot rules in IMA arch policy on powerpc
Status in The Ubuntu-power-systems project:
Fix Committed
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Focal:
Fix Committed
Status in linux source package in Groovy:
In Progress
Bug description:
SRU Justification:
==
[Impact]
* Currently the kernel module appended signature is verified twice
(finit_module) - once by the module_sig_check() and again by IMA.
* To prevent this the powerpc secure boot rules define an IMA
architecture specific policy rule only if CONFIG_MODULE_SIG_FORCE is
not enabled.
* But this doesn't take the ability into account of enabling
"sig_enforce" at the boot command line (module.sig_enforce=1).
* Including the IMA module appraise rule results in failing the
finit_module syscall, unless the module signing public key is loaded
onto the IMA keyring.
* This patch fixes secure boot policy rules to be based on
CONFIG_MODULE_SIG instead.
[Fix]
* fa4f3f56ccd28ac031ab275e673ed4098855fed4 fa4f3f56ccd2 "powerpc/ima:
Fix secure boot rules in ima arch policy"
[Test Case]
* Perform a secure boot on a powerpc system with
'module.sig_enforce=1' set at the boot command.
* If the IMA module appraise rule is included, the finit_module
syscall will fail (unless the module signing public key got loaded
onto the IMA keyring) without having the patch in place.
* The verification needs to be done by the IBM Power team.
[Regression Potential]
* There is (always) a certain regression risk with having code
changes, especially in the secure boot area.
* But this patch is limited to the powerpc platform and will not
affect any other architecture.
* It got discussed at
https://lore.kernel.org/r/1588342612-14532-1-git-send-email-na...@linux.ibm.com
before it became finally upstream accepted with kernel 5.7-rc7.
* The secure boot code itself wasn't really touched, rather than it's basis
for execution.
The IMA policy rule for module appraisal is now added only if
'CONFIG_MODULE_SIG' is not enabled (instead of CONFIG_MODULE_SIG_FORCE).
Hence the change is very limited and straightforward.
[Other]
* Since the patch got upstream with 5.7-rc7, it is already in groovy, hence
this SRU is for focal only.
__
== Comment: #0 - Michael Ranweiler - 2020-04-22
14:44:31 ==
+++ This bug was initially created as a clone of Bug #184073 +++
This bug is a follow on to LP 1866909 to address a missing piece -
only half the following patch was included in 5.4.0-24.28.
The upstream patch has an additional fix but it?s not critical for GA.
It can get included as part of bug fixes. It also affects only power.
The patch("powerpc/ima: fix secure boot rules in ima arch policy") is
posted to linux-integrity and linuxppc-dev mailing list
(https://lore.kernel.org/linux-integrity/1586549618-6106-1-git-send-
email-na...@linux.ibm.com/T/#u)
If there are any issues identified during further testing, they will
get opened as separate issue to be addressed later.
Thanks & Regards,
- Nayna
== Comment: #4 - Michael Ranweiler - 2020-05-11
02:23:35 ==
Updated posting:
https://lore.kernel.org/linux-integrity/1588342612-14532-1-git-send-
email-na...@linux.ibm.com/T/#u
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1877955/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1876844] Re: Speed up the process of s3 resume
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1876844 Title: Speed up the process of s3 resume Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-5.6 package in Ubuntu: New Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Status in linux-oem-5.6 source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Focal: New Status in linux-oem-5.6 source package in Focal: Fix Committed Status in linux-oem-osp1 source package in Focal: Invalid Bug description: [Impact] Process of s3 resume take 7s and it's too long which is over 5s. [Fix] Instead of using the supported speeds to determine whether to wait for Link training, check whether the port supports DLL Link Active reporting. The ports in question do not, so we'll wait only the 100 ms required for Ports that support Link speeds <= 5 GT/s. This of course assumes these Ports always train the Link within 100 ms even if they are operating at > 5 GT/s, which is not required by the spec. [test] With the patch, the total time s3 resume is 4454.244 ms which is smaller than 5s. [Regression Potential] Low. Follow the PCI spec to check whether the device supports DLL Link Active reporting, then choose the time of delay. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1876844/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1802691] Re: Slow send speed with Intel I219-V on Ubuntu 18.04.1
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1802691 Title: Slow send speed with Intel I219-V on Ubuntu 18.04.1 Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-oem-osp1 source package in Bionic: In Progress Status in linux source package in Eoan: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux-oem-5.6 source package in Focal: Fix Committed Status in linux source package in Groovy: In Progress Bug description: [Impact] The throughput measured by iperf3 is around 70% of 1Gbps (Intel I219-LM [8086:15b7]) I219 is a rather cheap NIC and it impacts its throughput if TSO(TCP segmentation offload) is enabled. [Fix] Disable TSO on NIC and move this task back to CPU fixes this issue. The impact of CPU loading is little to none. On target machine with Xeon(R) CPU E3-1505L v6 @ 2.20GHz(4c8t), the CPU usage of iperf3 increases from 1% to 4% [Verify] Origin [ ID] Interval Transfer Bandwidth Retr [ 4] 0.00-10.00 sec 918 MBytes 770 Mbits/sec 0 sender [ 4] 0.00-10.00 sec 916 MBytes 769 Mbits/sec receiver Becomes [ ID] Interval Transfer Bandwidth Retr [ 4] 0.00-10.00 sec 1.09 GBytes 936 Mbits/sec 0 sender [ 4] 0.00-10.00 sec 1.09 GBytes 934 Mbits/sec receiver [Regression Potential] Low, disable TSO on Ethernet chip will move the TCP segmentation task to CPU. This increase CPU loading a little bit, and should not introduce any regression. = Testing with iperf3 send speed is only 750mbps while receive speed is normal - 940mbps. Ubuntu 18.04.1 Msi b250m mortar --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: django 1016 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-11-09 (6 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: enp0s31f6 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: MSI MS-7A69 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-39-generic root=UUID=991b4393-3308-4615-97c8-9854b3bdc67e ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-39-generic N/A linux-backports-modules-4.15.0-39-generic N/A linux-firmware 1.173.1 RfKill: Tags: bionic Uname: Linux 4.15.0-39-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/29/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: A.60 dmi.board.asset.tag: Default string dmi.board.name: B250M MORTAR ARCTIC (MS-7A69) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrA.60:bd06/29/2018:svnMSI:pnMS-7A69:pvr2.0:rvnMSI:rnB250MMORTARARCTIC(MS-7A69):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.family: Default string dmi.product.name: MS-7A69 dmi.product.version: 2.0 dmi.sys.vendor: MSI To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1802691/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881120] Re: linux-oem-5.6-tools-common and -tools-host should be dropped
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1881120 Title: linux-oem-5.6-tools-common and -tools-host should be dropped Status in linux package in Ubuntu: Invalid Status in linux-oem-5.6 package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Status in linux-oem-5.6 source package in Focal: Fix Committed Bug description: [Impact] linux-oem-5.6 built -tools-common and -tools-host, which conflict with the master kernel versions. These shouldn't be built at all. [Test case] Check that upgrade removes the oem versions. [Regression potential] shouldn't be any -- Updating 20.04, unaware of details package linux-oem-5.6-tools-common 5.6.0-1008.8 [modified: usr/share /bash-completion/completions/bpftool usr/share/man/man1/cpupower.1.gz usr/share/man/man1/perf-annotate.1.gz usr/share/man/man1/perf- archive.1.gz usr/share/man/man1/perf-bench.1.gz usr/share/man/man1 /perf-buildid-cache.1.gz usr/share/man/man1/perf-buildid-list.1.gz usr/share/man/man1/perf-c2c.1.gz usr/share/man/man1/perf-config.1.gz usr/share/man/man1/perf-data.1.gz usr/share/man/man1/perf-diff.1.gz usr/share/man/man1/perf-evlist.1.gz usr/share/man/man1/perf- ftrace.1.gz usr/share/man/man1/perf-help.1.gz usr/share/man/man1/perf- inject.1.gz usr/share/man/man1/perf-kallsyms.1.gz usr/share/man/man1 /perf-kmem.1.gz usr/share/man/man1/perf-kvm.1.gz usr/share/man/man1 /perf-list.1.gz usr/share/man/man1/perf-lock.1.gz usr/share/man/man1 /perf-mem.1.gz usr/share/man/man1/perf-probe.1.gz usr/share/man/man1 /perf-record.1.gz usr/share/man/man1/perf-report.1.gz usr/share/man/man1/perf-sched.1.gz usr/share/man/man1/perf-script- perl.1.gz usr/share/man/man1/perf-script-python.1.gz usr/share/man/man1/perf-script.1.gz usr/share/man/man1/perf-stat.1.gz usr/share/man/man1/perf-test.1.gz usr/share/man/man1/perf- timechart.1.gz usr/share/man/man1/perf-top.1.gz usr/share/man/man1 /perf-trace.1.gz usr/share/man/man1/perf-version.1.gz usr/share/man/man1/perf.1.gz usr/share/man/man8/bpftool-map.8.gz usr/share/man/man8/bpftool-prog.8.gz usr/share/man/man8/bpftool.8.gz] failed to install/upgrade: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.4.0-31.35 ProblemType: Package DistroRelease: Ubuntu 20.04 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 CasperMD5CheckResult: skip Date: Thu May 28 07:43:09 2020 ErrorMessage: trying to overwrite '/usr/bin/acpidbg', which is also in package linux-tools-common 5.4.0-31.35 InstallationDate: Installed on 2020-04-28 (29 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: linux-oem-5.6 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881120/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1876707] Re: NULL pointer dereference in nvme reset work-queue when VMD raid mode and SecureBoot turned on simultaneously on TigerLake
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag 'verification-needed-focal' to 'verification-failed-focal'.
If verification is not done by 5 working days from today, this fix will
be dropped from the source code, and this bug will be closed.
See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how
to enable and use -proposed. Thank you!
** Tags added: verification-needed-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/1876707
Title:
NULL pointer dereference in nvme reset work-queue when VMD raid mode
and SecureBoot turned on simultaneously on TigerLake
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.6 source package in Focal:
Fix Committed
Status in linux source package in Groovy:
In Progress
Status in linux-oem-5.6 source package in Groovy:
Invalid
Bug description:
[SRU Justfication]
[Impact]
On platforms with NVMe attached to VMD controller, enable SecureBoot
would also force enable iommu:
DMAR: Intel-IOMMU force enabled due to platform opt in
While devices behind the VMD controller, also a PCI bridge, maybe forced
to use a DMA domain by current Intel-IOMMU driver, this may break some
relationships between sub devices behind VMD controller and between the
VMD controller and its children devices, and finally caused undefined
system behavior.
On devices at hand, this results in kernel NULL dereference at
__intel_map_single called from nvme_reset_work and fails root device
lookup at boot.
kernel: BUG: kernel NULL pointer dereference, address: 0018
kernel: #PF: supervisor read access in kernel mode
kernel: #PF: error_code(0x) - not-present page
kernel: PGD 0 P4D 0
kernel: Oops: [#2] SMP NOPTI
kernel: CPU: 1 PID: 254 Comm: kworker/u8:4 Tainted: G D W
5.7.0-050700rc3-generic #202004262131
kernel: Hardware name: Dell Inc. Vostro 5402/, BIOS 0.1.2 04/13/2020
kernel: Workqueue: nvme-reset-wq nvme_reset_work [nvme]
kernel: RIP: 0010:__intel_map_single+0xa3/0x1a0
...
[Fix]
Patchset[1] currently landed in iommu/next beginning with commit
327d5b2fee91 ("iommu/vt-d: Allow 32bit devices to uses DMA domain")
gives the solution to this problem. However, it's based on a massive
subsystem rewrite in patchset[2], currently in iommu/next beginning with
commit 441ff2ff8327 ("Move default domain allocation to separate
function").
On v5.6, it also depends on yet a few more patch series landed in
v5.7-rc1 beginning with commit 098accf2da94 ("iommu: Use C99 flexible
array in fwspec") that rewrote private data access, changed struct
names, etc.
Yet a few additional patches included as fixes to above changes.
[1]:
https://lore.kernel.org/linux-iommu/7928dd48-93da-62f0-b455-6e6b248d0...@linux.intel.com/
[2]:
https://lore.kernel.org/linux-iommu/20200429133712.31431-1-j...@8bytes.org/
[Test Case]
Test on platforms with VMD/NVMe and enable SecureBoot. System should
boot normally rather than into initramfs emergency shell.
[Regression Potential]
For unstable, all the patches are from iommu-next and will probably be
merged in next few -rc releases, so should be safe to place a LOW here.
For oem-5.6, the fixing patchset is depending on iommu group setup
refactoring that touched almost every architecture/platform uses iommu
although we would only care amd64 among them. Even with follow-up fixes
included, this is still a 60-patches change and deserves some more
attention. Medium.
== Original Bug Description ==
This is found on a Dell TigerLake platform that when VMD raid mode is
turned on along with SecureBoot, either deploy mode or audit mode,
kernel dumps warnings and null pointer deref errors at boot. While it
happens, it blocks systemd-udevd worker processes until killed due to
timeout. System still boots to multi-users.target.
Kernel bisect shows commit e3560ee4cfb2 ("iommu/vt-d: Remove VMD child
device sanity check") merged in v5.6-rc1 is the first commit to fail,
and is still reproducible on v5.7-rc3.
kernel: Secure boot disabled
...
kernel: [ cut here ]
kernel: WARNING: CPU: 1 PID: 8 at drivers/iommu/intel-iommu.c:625
domain_get_iommu+0x4b/0x60
kernel: Modules linked in: rc_core r8169(+) intel_lpss nvme crc32_pclmul(+)
psmouse intel_ish_ipc(+) i2c_hid i2c_i801(+) realtek idma64 drm virt_dma
intel_ishtp vmd(+) nvme_core hid video wmi pinctrl_tigerlake pinctrl_intel
kern
[Kernel-packages] [Bug 1850876] Re: CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan
OK, if there is no other problems, I will submit the SRU to ubuntu kernel to enable the V3D driver. thx. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1850876 Title: CONFIG_DRＭ_V3D is disabled for linux-raspi2 of eoan Status in linux-raspi2 package in Ubuntu: Fix Released Status in linux-raspi2 source package in Eoan: Triaged Bug description: We enabled DRM_VC4 in the linux-raspi2 of eoan, but disabled the DRM_V3D. In fact the DRM_V3D is crucial for graphical applications (such as ubuntu-desktop :) as it removes the graphical overhead from the cpu to the gpu, making the applications work much faster. Please refer to https://bugs.launchpad.net/ubuntu/+source/linux- raspi2/+bug/1848703/comments/32 [Impact] Users reported that we should enable the DRM_V3D, then the GPU will be fully used when running "ubuntu-desktop" [Fix] Enable the DRM_V3D, the v3d.ko will be built [Test Case] Users already tested it, it worked well. https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848703/comments/36 [Regression Risk] Low, I already did building test for arm64 and armhf, all passed. And uers already tested the kernel module, it worked as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1850876/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874698] Update Released
The verification of the Stable Release Update for alsa-ucm-conf 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 alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1874698 Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem Status in HWE Next: New Status in OEM Priority Project: Fix Committed Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in linux package in Ubuntu: Confirmed Status in alsa-ucm-conf source package in Focal: Fix Released Status in linux source package in Focal: Fix Committed Status in alsa-ucm-conf source package in Groovy: Fix Released Bug description: This is for alsa-ucm-conf: The patches are already in the mainline alsa-ucm-conf, so only sent the SRU for focal [Impact] On the machines without Intel HDMI, the sof driver will fail to initialize. [Fix] After fixing the kernel, we also need to change the ucm2 to make it support the machine without Intel hdmi audio. [Test Case] Boot the kernel on the machines without Intel HDMI audio, everything works well including the audio. [Regression Risk] Low, these 2 patches are already in the mainline alsa-ucm-conf. And we already tested them on 4 HP machines. This is for linux kernel: The patch is already in the oem-5.6 kernel and unstable kernel, so only sent the SRU for focal [Impact] On the machines without Intel HDMI, the sof driver will fail to initialize. [Fix] Intel upstream 2 patches in the kernel to fix it. [Test Case] Boot the kernel on the machines without Intel HDMI audio, everything works well including the audio. [Regression Risk] Low, these 2 patches are already in the mainline kernel. On Ubuntu 20.04, by default, sof-audio-pci is used. I only have "Dummy output" in pavucontrol. To fix this, I modified /etc/modprobe.d/alsa- base.conf and added "options snd-intel-dspcfg dsp_driver=1" so that now "snd-hda-intel" is loaded instead of sof-audio-pci. While the speakers are working fine, I do not have the internal microphone working (suspect a digital array). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: wittawat 2063 F pulseaudio /dev/snd/controlC0: wittawat 2063 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 24 12:42:32 2020 InstallationDate: Installed on 2020-04-23 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Mic, Left Symptom_Type: None of the above Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2019 dmi.bios.vendor: AMI dmi.bios.version: F.22 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8600 dmi.board.vendor: HP dmi.board.version: 44.41 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.22:bd12/09/2019:svnHP:pnOMENbyHPLaptop15-dh0xxx:pvr:rvnHP:rn8600:rvr44.41:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 15-dh0xxx dmi.product.sku: 7JX54EA#ABD dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-24T12:32:21.613996 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1874698/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
