[Kernel-packages] [Bug 1890186] Re: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument
Yes, Ctrl + zooms in and out. If we believe https://www.microsoft.com/accessories/en-ww/products/keyboards/natural- ergonomic-keyboard-4000/b2m-00012 (though my model is not B2M-00012 but 1048) , Microsoft intended the zoom slider on the keyboard to map to zoom in and out, too. -- 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/1890186 Title: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Won't Fix Bug description: I run an up-to-date Ubuntu 20.04.1 LTS "focal" with kernel 5.4.0-42-generic on Dell Latitude E6440. Upon examining the output of journalctl -b, I see this: Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Show Plymouth Boot Screen being skipped. Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Forward Password Requests to Plymouth Directory Watch being skipped. Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped. Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in File System Check on Root Device being skipped. Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped. Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Platform Persistent Storage Archival being skipped. Aug 03 19:22:15 pseudonymizedHostname kernel: [drm] radeon: dpm initialized Aug 03 19:22:15 pseudonymizedHostname kernel: [drm] GART: num cpu pages 524288, num gpu pages 524288 Aug 03 19:22:15 pseudonymizedHostname kernel: dell_laptop: Using dell-rbtn acpi driver for receiving events Aug 03 19:22:15 pseudonymizedHostname systemd-udevd[385]: event8: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument Aug 03 19:22:15 pseudonymizedHostname systemd-udevd[385]: event8: Failed to call EVIOCSKEYCODE with scan code 0xc022e, and key code 108: Invalid argument "Invalid argument" means that something goes wrong there, and I don't know what it is. On my laptop, event8 seems to be keyboard-related: $ sudo cat /proc/bus/input/devices | grep -C 5 event8 I: Bus=0003 Vendor=045e Product=00db Version=0111 N: Name="Microsoft Natural® Ergonomic Keyboard 4000" P: Phys=usb-:00:14.0-13.1/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-13/3-13.1/3-13.1:1.0/0003:045E:00DB.0002/input/input9 U: Uniq= H: Handlers=sysrq kbd event8 leds B: PROP=0 B: EV=120013 B: KEY=10007 ff8007ff febeffdff3cf fffe B: MSC=10 B: LED=107 The issue report https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1754921 is probably related but marked as a duplicate of a no longer existing issue report (#1750855). The report https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1597415 describes a similar issue for older kernels; the differences pertain to error message, error code, input..., and, opposed to #19 there, I have no Windows partitions (except /boot/efi vfat) in /etc/fstab; mine is not a dual-boot machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890186/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1890186] Re: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument
@ddstreet Thank for the explanation. (Myself, I don't know why the keyboard behaves this way; I can imagine any option, e.g., a glitch of the keyboard firmware or hardware, an unintended bug introduced by the developers of the manufacturer, a cost-reducing design of the manufacturer, or an politically intentional (against the standard!) design of the manufacturer.) As for the zoom in/out, I meant this: https://support.mozilla.org/en-US/kb/font-size-and-zoom-increase-size- of-web-pages -- 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/1890186 Title: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Won't Fix Bug description: I run an up-to-date Ubuntu 20.04.1 LTS "focal" with kernel 5.4.0-42-generic on Dell Latitude E6440. Upon examining the output of journalctl -b, I see this: Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Show Plymouth Boot Screen being skipped. Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Forward Password Requests to Plymouth Directory Watch being skipped. Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped. Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in File System Check on Root Device being skipped. Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped. Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Platform Persistent Storage Archival being skipped. Aug 03 19:22:15 pseudonymizedHostname kernel: [drm] radeon: dpm initialized Aug 03 19:22:15 pseudonymizedHostname kernel: [drm] GART: num cpu pages 524288, num gpu pages 524288 Aug 03 19:22:15 pseudonymizedHostname kernel: dell_laptop: Using dell-rbtn acpi driver for receiving events Aug 03 19:22:15 pseudonymizedHostname systemd-udevd[385]: event8: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument Aug 03 19:22:15 pseudonymizedHostname systemd-udevd[385]: event8: Failed to call EVIOCSKEYCODE with scan code 0xc022e, and key code 108: Invalid argument "Invalid argument" means that something goes wrong there, and I don't know what it is. On my laptop, event8 seems to be keyboard-related: $ sudo cat /proc/bus/input/devices | grep -C 5 event8 I: Bus=0003 Vendor=045e Product=00db Version=0111 N: Name="Microsoft Natural® Ergonomic Keyboard 4000" P: Phys=usb-:00:14.0-13.1/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-13/3-13.1/3-13.1:1.0/0003:045E:00DB.0002/input/input9 U: Uniq= H: Handlers=sysrq kbd event8 leds B: PROP=0 B: EV=120013 B: KEY=10007 ff8007ff febeffdff3cf fffe B: MSC=10 B: LED=107 The issue report https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1754921 is probably related but marked as a duplicate of a no longer existing issue report (#1750855). The report https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1597415 describes a similar issue for older kernels; the differences pertain to error message, error code, input..., and, opposed to #19 there, I have no Windows partitions (except /boot/efi vfat) in /etc/fstab; mine is not a dual-boot machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890186/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1890186] Re: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument
@ddstreet Thanks for the feedback. The keyboard has “Microsoft® Natural® Ergonomic Keyboard 4000 v1.0”, “Model 1048” printed on its bottom. The keyboard looks pretty standard to me from outside. Do you really mean it's broken? Is any combination of the sliding key with any modifier key(s) (such as Ctrl, Alt, or Shift) supposed to zoom in/out say, in the Firefox Web browser? -- 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/1890186 Title: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Won't Fix Bug description: I run an up-to-date Ubuntu 20.04.1 LTS "focal" with kernel 5.4.0-42-generic on Dell Latitude E6440. Upon examining the output of journalctl -b, I see this: Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Show Plymouth Boot Screen being skipped. Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Forward Password Requests to Plymouth Directory Watch being skipped. Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped. Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in File System Check on Root Device being skipped. Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped. Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Platform Persistent Storage Archival being skipped. Aug 03 19:22:15 pseudonymizedHostname kernel: [drm] radeon: dpm initialized Aug 03 19:22:15 pseudonymizedHostname kernel: [drm] GART: num cpu pages 524288, num gpu pages 524288 Aug 03 19:22:15 pseudonymizedHostname kernel: dell_laptop: Using dell-rbtn acpi driver for receiving events Aug 03 19:22:15 pseudonymizedHostname systemd-udevd[385]: event8: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument Aug 03 19:22:15 pseudonymizedHostname systemd-udevd[385]: event8: Failed to call EVIOCSKEYCODE with scan code 0xc022e, and key code 108: Invalid argument "Invalid argument" means that something goes wrong there, and I don't know what it is. On my laptop, event8 seems to be keyboard-related: $ sudo cat /proc/bus/input/devices | grep -C 5 event8 I: Bus=0003 Vendor=045e Product=00db Version=0111 N: Name="Microsoft Natural® Ergonomic Keyboard 4000" P: Phys=usb-:00:14.0-13.1/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-13/3-13.1/3-13.1:1.0/0003:045E:00DB.0002/input/input9 U: Uniq= H: Handlers=sysrq kbd event8 leds B: PROP=0 B: EV=120013 B: KEY=10007 ff8007ff febeffdff3cf fffe B: MSC=10 B: LED=107 The issue report https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1754921 is probably related but marked as a duplicate of a no longer existing issue report (#1750855). The report https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1597415 describes a similar issue for older kernels; the differences pertain to error message, error code, input..., and, opposed to #19 there, I have no Windows partitions (except /boot/efi vfat) in /etc/fstab; mine is not a dual-boot machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890186/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1890186] Re: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument
** 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/1890186 Title: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: I run an up-to-date Ubuntu 20.04.1 LTS "focal" with kernel 5.4.0-42-generic on Dell Latitude E6440. Upon examining the output of journalctl -b, I see this: Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Show Plymouth Boot Screen being skipped. Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Forward Password Requests to Plymouth Directory Watch being skipped. Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped. Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in File System Check on Root Device being skipped. Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped. Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Platform Persistent Storage Archival being skipped. Aug 03 19:22:15 pseudonymizedHostname kernel: [drm] radeon: dpm initialized Aug 03 19:22:15 pseudonymizedHostname kernel: [drm] GART: num cpu pages 524288, num gpu pages 524288 Aug 03 19:22:15 pseudonymizedHostname kernel: dell_laptop: Using dell-rbtn acpi driver for receiving events Aug 03 19:22:15 pseudonymizedHostname systemd-udevd[385]: event8: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument Aug 03 19:22:15 pseudonymizedHostname systemd-udevd[385]: event8: Failed to call EVIOCSKEYCODE with scan code 0xc022e, and key code 108: Invalid argument "Invalid argument" means that something goes wrong there, and I don't know what it is. On my laptop, event8 seems to be keyboard-related: $ sudo cat /proc/bus/input/devices | grep -C 5 event8 I: Bus=0003 Vendor=045e Product=00db Version=0111 N: Name="Microsoft Natural® Ergonomic Keyboard 4000" P: Phys=usb-:00:14.0-13.1/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-13/3-13.1/3-13.1:1.0/0003:045E:00DB.0002/input/input9 U: Uniq= H: Handlers=sysrq kbd event8 leds B: PROP=0 B: EV=120013 B: KEY=10007 ff8007ff febeffdff3cf fffe B: MSC=10 B: LED=107 The issue report https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1754921 is probably related but marked as a duplicate of a no longer existing issue report (#1750855). The report https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1597415 describes a similar issue for older kernels; the differences pertain to error message, error code, input..., and, opposed to #19 there, I have no Windows partitions (except /boot/efi vfat) in /etc/fstab; mine is not a dual-boot machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890186/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1890186] Re: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument
In the meantime, I updated Ubuntu to groovy 20.10. My dmesg is [0.00] microcode: microcode updated early to revision 0x28, date = 2019-11-12 [0.00] Linux version 5.8.0-33-generic (buildd@lgw01-amd64-036) (gcc (Ubuntu 10.2.0-13ubuntu1) 10.2.0, GNU ld (GNU Binutils for Ubuntu) 2.35.1) #36-Ubuntu SMP Wed Dec 9 09:14:40 UTC 2020 (Ubuntu 5.8.0-33.36-generic 5.8.17) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.8.0-33-generic root=UUID=e5bf110c-cf26-4c1f-8f95-84c054455347 ro [0.00] KERNEL supported cpus: [0.00] Intel GenuineIntel [0.00] AMD AuthenticAMD [0.00] Hygon HygonGenuine [0.00] Centaur CentaurHauls [0.00] zhaoxin Shanghai [0.00] x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers' [0.00] x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers' [0.00] x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers' [0.00] x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256 [0.00] x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'standard' format. [0.00] BIOS-provided physical RAM map: [0.00] BIOS-e820: [mem 0x-0x0004efff] usable [0.00] BIOS-e820: [mem 0x0004f000-0x0004] reserved [0.00] BIOS-e820: [mem 0x0005-0x0009efff] usable [0.00] BIOS-e820: [mem 0x0009f000-0x0009] reserved [0.00] BIOS-e820: [mem 0x0010-0xbead8fff] usable [0.00] BIOS-e820: [mem 0xbead9000-0xbead] ACPI NVS [0.00] BIOS-e820: [mem 0xbeae-0xbf4d4fff] usable [0.00] BIOS-e820: [mem 0xbf4d5000-0xbf9b9fff] reserved [0.00] BIOS-e820: [mem 0xbf9ba000-0xc7db2fff] usable [0.00] BIOS-e820: [mem 0xc7db3000-0xc7ff] reserved [0.00] BIOS-e820: [mem 0xc800-0xc8758fff] usable [0.00] BIOS-e820: [mem 0xc8759000-0xc87f] reserved [0.00] BIOS-e820: [mem 0xc880-0xc8f92fff] usable [0.00] BIOS-e820: [mem 0xc8f93000-0xc8ff] ACPI data [0.00] BIOS-e820: [mem 0xc900-0xca6f9fff] usable [0.00] BIOS-e820: [mem 0xca6fa000-0xca7f] ACPI NVS [0.00] BIOS-e820: [mem 0xca80-0xcbce8fff] usable [0.00] BIOS-e820: [mem 0xcbce9000-0xcbff] reserved [0.00] BIOS-e820: [mem 0xcd00-0xcf1f] reserved [0.00] BIOS-e820: [mem 0xf800-0xfbff] reserved [0.00] BIOS-e820: [mem 0xfec0-0xfec00fff] reserved [0.00] BIOS-e820: [mem 0xfed0-0xfed03fff] reserved [0.00] BIOS-e820: [mem 0xfed1c000-0xfed1] reserved [0.00] BIOS-e820: [mem 0xfee0-0xfee00fff] reserved [0.00] BIOS-e820: [mem 0xff00-0x] reserved [0.00] BIOS-e820: [mem 0x0001-0x00042edf] usable [0.00] NX (Execute Disable) protection: active [0.00] e820: update [mem 0xc5467018-0xc546fa57] usable ==> usable [0.00] e820: update [mem 0xc5467018-0xc546fa57] usable ==> usable [0.00] e820: update [mem 0xc5456018-0xc5466057] usable ==> usable [0.00] e820: update [mem 0xc5456018-0xc5466057] usable ==> usable [0.00] e820: update [mem 0xc5445018-0xc5455457] usable ==> usable [0.00] e820: update [mem 0xc5445018-0xc5455457] usable ==> usable [0.00] extended physical RAM map: [0.00] reserve setup_data: [mem 0x-0x0004efff] usable [0.00] reserve setup_data: [mem 0x0004f000-0x0004] reserved [0.00] reserve setup_data: [mem 0x0005-0x0009efff] usable [0.00] reserve setup_data: [mem 0x0009f000-0x0009] reserved [0.00] reserve setup_data: [mem 0x0010-0xbead8fff] usable [0.00] reserve setup_data: [mem 0xbead9000-0xbead] ACPI NVS [0.00] reserve setup_data: [mem 0xbeae-0xbf4d4fff] usable [0.00] reserve setup_data: [mem 0xbf4d5000-0xbf9b9fff] reserved [0.00] reserve setup_data: [mem 0xbf9ba000-0xc5445017] usable [0.00] reserve setup_data: [mem 0xc5445018-0xc5455457] usable [0.00] reserve setup_data: [mem 0xc5455458-0xc5456017] usable [0.00] reserve setup_data: [mem 0xc5456018-0xc5466057] usable [0.00] reserve setup_data: [mem 0xc5466058-0xc5467017] usable [0.00] reserve setup_data: [mem 0xc5467018-0xc546fa57] usable [0.00]
[Kernel-packages] [Bug 1890186] Re: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument
This command would disclose potentially sensitive information of a production machine to the public; I won't do it unless given an opportunity to anonymize the results upfront. ** 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/1890186 Title: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: New Bug description: I run an up-to-date Ubuntu 20.04.1 LTS "focal" with kernel 5.4.0-42-generic on Dell Latitude E6440. Upon examining the output of journalctl -b, I see this: Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Show Plymouth Boot Screen being skipped. Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Forward Password Requests to Plymouth Directory Watch being skipped. Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Set Up Additional Binary Formats being skipped. Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in File System Check on Root Device being skipped. Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Rebuild Hardware Database being skipped. Aug 03 19:22:15 pseudonymizedHostname systemd[1]: Condition check resulted in Platform Persistent Storage Archival being skipped. Aug 03 19:22:15 pseudonymizedHostname kernel: [drm] radeon: dpm initialized Aug 03 19:22:15 pseudonymizedHostname kernel: [drm] GART: num cpu pages 524288, num gpu pages 524288 Aug 03 19:22:15 pseudonymizedHostname kernel: dell_laptop: Using dell-rbtn acpi driver for receiving events Aug 03 19:22:15 pseudonymizedHostname systemd-udevd[385]: event8: Failed to call EVIOCSKEYCODE with scan code 0xc022d, and key code 103: Invalid argument Aug 03 19:22:15 pseudonymizedHostname systemd-udevd[385]: event8: Failed to call EVIOCSKEYCODE with scan code 0xc022e, and key code 108: Invalid argument "Invalid argument" means that something goes wrong there, and I don't know what it is. On my laptop, event8 seems to be keyboard-related: $ sudo cat /proc/bus/input/devices | grep -C 5 event8 I: Bus=0003 Vendor=045e Product=00db Version=0111 N: Name="Microsoft Natural® Ergonomic Keyboard 4000" P: Phys=usb-:00:14.0-13.1/input0 S: Sysfs=/devices/pci:00/:00:14.0/usb3/3-13/3-13.1/3-13.1:1.0/0003:045E:00DB.0002/input/input9 U: Uniq= H: Handlers=sysrq kbd event8 leds B: PROP=0 B: EV=120013 B: KEY=10007 ff8007ff febeffdff3cf fffe B: MSC=10 B: LED=107 The issue report https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1754921 is probably related but marked as a duplicate of a no longer existing issue report (#1750855). The report https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1597415 describes a similar issue for older kernels; the differences pertain to error message, error code, input..., and, opposed to #19 there, I have no Windows partitions (except /boot/efi vfat) in /etc/fstab; mine is not a dual-boot machine. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890186/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1890467] Re: wmi_bus wmi_bus-PNP0C14:00: WQBC data block query control method not found
By the way, I know the BIOS is outdated (A21 instead of A24), but I failed to update it via FreeDOS process. (The manual https://wiki.ubuntuusers.de/BIOS_aktualisieren is partially out of date in this point or I do something wrong, but it's a different issue anyway, having little to do with this very 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/1890467 Title: wmi_bus wmi_bus-PNP0C14:00: WQBC data block query control method not found Status in linux package in Ubuntu: Confirmed Bug description: I run the kernel 5.4.0-42-generic on a fully up-to-date Ubuntu "focal" on Dell Latitude E6440. While scrolling through the output of `journalctl -b` I came across a warning (marked yellow): [0.659825] wmi_bus wmi_bus-PNP0C14:00: WQBC data block query control method not found Now, since this is a warning, I get, ergo, warned. What is it that I get warned about? Is it just a printf or is some action required? As every computer, the laptop suffers from various problems from time to time (e.g., boot or wakeup silently hangs up while the manufacturer splash screen is displayed), so, I don't know whether this message could be related to any of such problems. Here is the context of this warning in dmesg: # dmesg | grep -B 10 -A 5 "method not found" [0.518379] rtc_cmos 00:02: setting system clock to 2020-08-05T15:23:54 UTC (1596641034) [0.519455] Freeing unused decrypted memory: 2040K [0.520119] Freeing unused kernel image memory: 2712K [0.531430] Write protecting the kernel read-only data: 22528k [0.532242] Freeing unused kernel image memory: 2008K [0.532805] Freeing unused kernel image memory: 1192K [0.540186] x86/mm: Checked W+X mappings: passed, no W+X pages found. [0.540514] x86/mm: Checking user space page tables [0.547468] x86/mm: Checked W+X mappings: passed, no W+X pages found. [0.547786] Run /init as init process [0.659825] wmi_bus wmi_bus-PNP0C14:00: WQBC data block query control method not found [0.659921] ACPI Warning: SystemIO range 0x1828-0x182F conflicts with OpRegion 0x1800-0x183F (\_SB.PCI0.EHC2.E1PM) (20190816/utaddress-204) [0.661768] ACPI Warning: SystemIO range 0x1828-0x182F conflicts with OpRegion 0x1800-0x183F (\_SB.PCI0.EHC1.E1PM) (20190816/utaddress-204) [0.663121] ACPI Warning: SystemIO range 0x1828-0x182F conflicts with OpRegion 0x1800-0x187F (\PMIO) (20190816/utaddress-204) [0.664516] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [0.666167] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k Some more info: # ls -la /sys/devices/platform/PNP0C14:00 drwxr-xr-x 4 root root0 Aug 5 17:23 . drwxr-xr-x 29 root root0 Aug 5 17:23 .. lrwxrwxrwx 1 root root0 Aug 5 17:23 driver -> ../../../bus/platform/drivers/acpi-wmi -rw-r--r-- 1 root root 4096 Aug 5 18:09 driver_override lrwxrwxrwx 1 root root0 Aug 5 18:09 firmware_node -> ../../LNXSYSTM:00/LNXSYBUS:00/PNP0C14:00 -r--r--r-- 1 root root 4096 Aug 5 18:09 modalias drwxr-xr-x 2 root root0 Aug 5 18:09 power lrwxrwxrwx 1 root root0 Aug 5 17:23 subsystem -> ../../../bus/platform -rw-r--r-- 1 root root 4096 Aug 5 17:23 uevent drwxr-xr-x 3 root root0 Aug 5 17:23 wmi_bus # To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890467/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1890467] Re: wmi_bus wmi_bus-PNP0C14:00: WQBC data block query control method not found
Result of `sudo acpidump > acpi.log` attached. As for USB issues: 1. I sometimes experience bad contact to my iPhone when I charge it using a USB port. This seems to be a physically bad contact to me, however, but I cannot tell for sure. 2. Another issue is that after a USB thumb drive has been unmounted via the `unmount` command, the written data may be yet in the process of being transferred, so simply taking the drive out immediately after unmounting would probably damage the file system or the drive itself or both. I need to say `udisksctl power-off -b /dev/sdb` and wait for termination to make sure that the device is really safe to unplug. As for wake-up, the laptop seldom refuses to wake up and freezes instead. I simply gave the issue as an example of what goes wrong (there are dozens of such small issues). ** Attachment added: "Result of `sudo acpidump > acpi.log`." https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890467/+attachment/5399096/+files/acpi.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/1890467 Title: wmi_bus wmi_bus-PNP0C14:00: WQBC data block query control method not found Status in linux package in Ubuntu: Confirmed Bug description: I run the kernel 5.4.0-42-generic on a fully up-to-date Ubuntu "focal" on Dell Latitude E6440. While scrolling through the output of `journalctl -b` I came across a warning (marked yellow): [0.659825] wmi_bus wmi_bus-PNP0C14:00: WQBC data block query control method not found Now, since this is a warning, I get, ergo, warned. What is it that I get warned about? Is it just a printf or is some action required? As every computer, the laptop suffers from various problems from time to time (e.g., boot or wakeup silently hangs up while the manufacturer splash screen is displayed), so, I don't know whether this message could be related to any of such problems. Here is the context of this warning in dmesg: # dmesg | grep -B 10 -A 5 "method not found" [0.518379] rtc_cmos 00:02: setting system clock to 2020-08-05T15:23:54 UTC (1596641034) [0.519455] Freeing unused decrypted memory: 2040K [0.520119] Freeing unused kernel image memory: 2712K [0.531430] Write protecting the kernel read-only data: 22528k [0.532242] Freeing unused kernel image memory: 2008K [0.532805] Freeing unused kernel image memory: 1192K [0.540186] x86/mm: Checked W+X mappings: passed, no W+X pages found. [0.540514] x86/mm: Checking user space page tables [0.547468] x86/mm: Checked W+X mappings: passed, no W+X pages found. [0.547786] Run /init as init process [0.659825] wmi_bus wmi_bus-PNP0C14:00: WQBC data block query control method not found [0.659921] ACPI Warning: SystemIO range 0x1828-0x182F conflicts with OpRegion 0x1800-0x183F (\_SB.PCI0.EHC2.E1PM) (20190816/utaddress-204) [0.661768] ACPI Warning: SystemIO range 0x1828-0x182F conflicts with OpRegion 0x1800-0x183F (\_SB.PCI0.EHC1.E1PM) (20190816/utaddress-204) [0.663121] ACPI Warning: SystemIO range 0x1828-0x182F conflicts with OpRegion 0x1800-0x187F (\PMIO) (20190816/utaddress-204) [0.664516] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [0.666167] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k Some more info: # ls -la /sys/devices/platform/PNP0C14:00 drwxr-xr-x 4 root root0 Aug 5 17:23 . drwxr-xr-x 29 root root0 Aug 5 17:23 .. lrwxrwxrwx 1 root root0 Aug 5 17:23 driver -> ../../../bus/platform/drivers/acpi-wmi -rw-r--r-- 1 root root 4096 Aug 5 18:09 driver_override lrwxrwxrwx 1 root root0 Aug 5 18:09 firmware_node -> ../../LNXSYSTM:00/LNXSYBUS:00/PNP0C14:00 -r--r--r-- 1 root root 4096 Aug 5 18:09 modalias drwxr-xr-x 2 root root0 Aug 5 18:09 power lrwxrwxrwx 1 root root0 Aug 5 17:23 subsystem -> ../../../bus/platform -rw-r--r-- 1 root root 4096 Aug 5 17:23 uevent drwxr-xr-x 3 root root0 Aug 5 17:23 wmi_bus # To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890467/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1890467] Re: wmi_bus wmi_bus-PNP0C14:00: WQBC data block query control method not found
I won't run the suggested command (apport-collect 1890467), as is doesn't anonymize or pseudonymize my data or the data of the laptop sufficiently. If given an opportunity to do so manually and paste the result using the Web interface, I will gladly proceed. ** 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/1890467 Title: wmi_bus wmi_bus-PNP0C14:00: WQBC data block query control method not found Status in linux package in Ubuntu: Confirmed Bug description: I run the kernel 5.4.0-42-generic on a fully up-to-date Ubuntu "focal" on Dell Latitude E6440. While scrolling through the output of `journalctl -b` I came across a warning (marked yellow): [0.659825] wmi_bus wmi_bus-PNP0C14:00: WQBC data block query control method not found Now, since this is a warning, I get, ergo, warned. What is it that I get warned about? Is it just a printf or is some action required? As every computer, the laptop suffers from various problems from time to time (e.g., boot or wakeup silently hangs up while the manufacturer splash screen is displayed), so, I don't know whether this message could be related to any of such problems. Here is the context of this warning in dmesg: # dmesg | grep -B 10 -A 5 "method not found" [0.518379] rtc_cmos 00:02: setting system clock to 2020-08-05T15:23:54 UTC (1596641034) [0.519455] Freeing unused decrypted memory: 2040K [0.520119] Freeing unused kernel image memory: 2712K [0.531430] Write protecting the kernel read-only data: 22528k [0.532242] Freeing unused kernel image memory: 2008K [0.532805] Freeing unused kernel image memory: 1192K [0.540186] x86/mm: Checked W+X mappings: passed, no W+X pages found. [0.540514] x86/mm: Checking user space page tables [0.547468] x86/mm: Checked W+X mappings: passed, no W+X pages found. [0.547786] Run /init as init process [0.659825] wmi_bus wmi_bus-PNP0C14:00: WQBC data block query control method not found [0.659921] ACPI Warning: SystemIO range 0x1828-0x182F conflicts with OpRegion 0x1800-0x183F (\_SB.PCI0.EHC2.E1PM) (20190816/utaddress-204) [0.661768] ACPI Warning: SystemIO range 0x1828-0x182F conflicts with OpRegion 0x1800-0x183F (\_SB.PCI0.EHC1.E1PM) (20190816/utaddress-204) [0.663121] ACPI Warning: SystemIO range 0x1828-0x182F conflicts with OpRegion 0x1800-0x187F (\PMIO) (20190816/utaddress-204) [0.664516] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [0.666167] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k Some more info: # ls -la /sys/devices/platform/PNP0C14:00 drwxr-xr-x 4 root root0 Aug 5 17:23 . drwxr-xr-x 29 root root0 Aug 5 17:23 .. lrwxrwxrwx 1 root root0 Aug 5 17:23 driver -> ../../../bus/platform/drivers/acpi-wmi -rw-r--r-- 1 root root 4096 Aug 5 18:09 driver_override lrwxrwxrwx 1 root root0 Aug 5 18:09 firmware_node -> ../../LNXSYSTM:00/LNXSYBUS:00/PNP0C14:00 -r--r--r-- 1 root root 4096 Aug 5 18:09 modalias drwxr-xr-x 2 root root0 Aug 5 18:09 power lrwxrwxrwx 1 root root0 Aug 5 17:23 subsystem -> ../../../bus/platform -rw-r--r-- 1 root root 4096 Aug 5 17:23 uevent drwxr-xr-x 3 root root0 Aug 5 17:23 wmi_bus # To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890467/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1890467] [NEW] wmi_bus wmi_bus-PNP0C14:00: WQBC data block query control method not found
Public bug reported: I run the kernel 5.4.0-42-generic on a fully up-to-date Ubuntu "focal" on Dell Latitude E6440. While scrolling through the output of `journalctl -b` I came across a warning (marked yellow): [0.659825] wmi_bus wmi_bus-PNP0C14:00: WQBC data block query control method not found Now, since this is a warning, I get, ergo, warned. What is it that I get warned about? Is it just a printf or is some action required? As every computer, the laptop suffers from various problems from time to time (e.g., boot or wakeup silently hangs up while the manufacturer splash screen is displayed), so, I don't know whether this message could be related to any of such problems. Here is the context of this warning in dmesg: # dmesg | grep -B 10 -A 5 "method not found" [0.518379] rtc_cmos 00:02: setting system clock to 2020-08-05T15:23:54 UTC (1596641034) [0.519455] Freeing unused decrypted memory: 2040K [0.520119] Freeing unused kernel image memory: 2712K [0.531430] Write protecting the kernel read-only data: 22528k [0.532242] Freeing unused kernel image memory: 2008K [0.532805] Freeing unused kernel image memory: 1192K [0.540186] x86/mm: Checked W+X mappings: passed, no W+X pages found. [0.540514] x86/mm: Checking user space page tables [0.547468] x86/mm: Checked W+X mappings: passed, no W+X pages found. [0.547786] Run /init as init process [0.659825] wmi_bus wmi_bus-PNP0C14:00: WQBC data block query control method not found [0.659921] ACPI Warning: SystemIO range 0x1828-0x182F conflicts with OpRegion 0x1800-0x183F (\_SB.PCI0.EHC2.E1PM) (20190816/utaddress-204) [0.661768] ACPI Warning: SystemIO range 0x1828-0x182F conflicts with OpRegion 0x1800-0x183F (\_SB.PCI0.EHC1.E1PM) (20190816/utaddress-204) [0.663121] ACPI Warning: SystemIO range 0x1828-0x182F conflicts with OpRegion 0x1800-0x187F (\PMIO) (20190816/utaddress-204) [0.664516] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [0.666167] e1000e: Intel(R) PRO/1000 Network Driver - 3.2.6-k Some more info: # ls -la /sys/devices/platform/PNP0C14:00 drwxr-xr-x 4 root root0 Aug 5 17:23 . drwxr-xr-x 29 root root0 Aug 5 17:23 .. lrwxrwxrwx 1 root root0 Aug 5 17:23 driver -> ../../../bus/platform/drivers/acpi-wmi -rw-r--r-- 1 root root 4096 Aug 5 18:09 driver_override lrwxrwxrwx 1 root root0 Aug 5 18:09 firmware_node -> ../../LNXSYSTM:00/LNXSYBUS:00/PNP0C14:00 -r--r--r-- 1 root root 4096 Aug 5 18:09 modalias drwxr-xr-x 2 root root0 Aug 5 18:09 power lrwxrwxrwx 1 root root0 Aug 5 17:23 subsystem -> ../../../bus/platform -rw-r--r-- 1 root root 4096 Aug 5 17:23 uevent drwxr-xr-x 3 root root0 Aug 5 17:23 wmi_bus # ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: focal ** Description changed: I run the kernel 5.4.0-42-generic on a fully up-to-date Ubuntu "focal" on Dell Latitude E6440. - While scrolling through the output of `journalctl -b` I came across a warning (marked yellow): + While scrolling through the output of `journalctl -b` I came across the following warning (marked yellow): [0.659825] wmi_bus wmi_bus-PNP0C14:00: WQBC data block query control method not found Now, since this is a warning, I get, ergo, warned. What is it that I get warned about? Is it just a printf or is some action required? Here is the context of this warning in dmesg: # dmesg | grep -B 10 -A 5 "method not found" [0.518379] rtc_cmos 00:02: setting system clock to 2020-08-05T15:23:54 UTC (1596641034) [0.519455] Freeing unused decrypted memory: 2040K [0.520119] Freeing unused kernel image memory: 2712K [0.531430] Write protecting the kernel read-only data: 22528k [0.532242] Freeing unused kernel image memory: 2008K [0.532805] Freeing unused kernel image memory: 1192K [0.540186] x86/mm: Checked W+X mappings: passed, no W+X pages found. [0.540514] x86/mm: Checking user space page tables [0.547468] x86/mm: Checked W+X mappings: passed, no W+X pages found. [0.547786] Run /init as init process [0.659825] wmi_bus wmi_bus-PNP0C14:00: WQBC data block query control method not found [0.659921] ACPI Warning: SystemIO range 0x1828-0x182F conflicts with OpRegion 0x1800-0x183F (\_SB.PCI0.EHC2.E1PM) (20190816/utaddress-204) [0.661768] ACPI Warning: SystemIO range 0x1828-0x182F conflicts with OpRegion 0x1800-0x183F (\_SB.PCI0.EHC1.E1PM) (20190816/utaddress-204) [0.663121] ACPI Warning: SystemIO range 0x1828-0x182F conflicts with OpRegion 0x1800-0x187F (\PMIO)
[Kernel-packages] [Bug 1835660] Re: initramfs unpacking failed
I recall that on one of my machines I had exactly the same situation as reported in #20 and #21 up to the timings (5.3.0-26-generic in Ubuntu 19.10 with EFI Secure Boot and dual boot with Windows 10, fastboot/hibernation disabled, LZ4 image by default, booting failed often, booting succeeded upon reinstall with EFI secure boot). Unfortunately, I don't have this machine any longer. @mario-gleirscher would probably be of help if they provide us with some debugging when asked by the Ubuntu maintainers. On another machine, I still have this annoying printf in dmesg (and journalctl -b): [0.215092] NET: Registered protocol family 1 [0.215096] NET: Registered protocol family 44 [0.215105] pci :00:02.0: Video device with shadowed ROM at [mem 0x000c-0x000d] [0.215670] PCI: CLS 64 bytes, default 64 [0.215696] Trying to unpack rootfs image as initramfs... [0.303126] Initramfs unpacking failed: Decoding failed [0.306614] Freeing initrd memory: 48364K I run 5.4.0-42-generic in Ubuntu 20.04.1 LTS focal. As for me, this issue seems to simply uselessly burn processor cycles (and, as every such issue, indirectly generate superfluous carbon dioxide); there is a potential for optimization here. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 1837326] Re: platform eisa.0: EISA: Cannot allocate resource for mainboard
Same for me here on Ubuntu focal. # uname -a Linux undisclosedHostName 5.4.0-42-generic #46-Ubuntu SMP Fri Jul 10 00:24:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Jul 27 14:42:41 undisclosedHostName kernel: device-mapper: uevent: version 1.0.3 Jul 27 14:42:41 undisclosedHostName kernel: device-mapper: ioctl: 4.41.0-ioctl (2019-09-16) initialised: dm-de...@redhat.com Jul 27 14:42:41 undisclosedHostName kernel: platform eisa.0: Probing EISA bus 0 Jul 27 14:42:41 undisclosedHostName kernel: platform eisa.0: EISA: Cannot allocate resource for mainboard Jul 27 14:42:41 undisclosedHostName kernel: input: AT Translated Set 2 keyboard as /devices/platform/i8042/serio0/input/input4 Jul 27 14:42:41 undisclosedHostName kernel: platform eisa.0: Cannot allocate resource for EISA slot 1 Jul 27 14:42:41 undisclosedHostName kernel: platform eisa.0: Cannot allocate resource for EISA slot 2 Jul 27 14:42:41 undisclosedHostName kernel: platform eisa.0: Cannot allocate resource for EISA slot 3 Jul 27 14:42:41 undisclosedHostName kernel: platform eisa.0: Cannot allocate resource for EISA slot 4 Jul 27 14:42:41 undisclosedHostName kernel: platform eisa.0: Cannot allocate resource for EISA slot 5 Jul 27 14:42:41 undisclosedHostName kernel: platform eisa.0: Cannot allocate resource for EISA slot 6 Jul 27 14:42:41 undisclosedHostName kernel: platform eisa.0: Cannot allocate resource for EISA slot 7 Jul 27 14:42:41 undisclosedHostName kernel: platform eisa.0: Cannot allocate resource for EISA slot 8 Jul 27 14:42:41 undisclosedHostName kernel: platform eisa.0: EISA: Detected 0 cards Certain lines (listed again below) are marked in color. If they are harmless, why mark them? Jul 27 14:42:41 undisclosedHostName kernel: platform eisa.0: EISA: Cannot allocate resource for mainboard Jul 27 14:42:41 undisclosedHostName kernel: platform eisa.0: Cannot allocate resource for EISA slot 1 Jul 27 14:42:41 undisclosedHostName kernel: platform eisa.0: Cannot allocate resource for EISA slot 2 Jul 27 14:42:41 undisclosedHostName kernel: platform eisa.0: Cannot allocate resource for EISA slot 3 Jul 27 14:42:41 undisclosedHostName kernel: platform eisa.0: Cannot allocate resource for EISA slot 4 Jul 27 14:42:41 undisclosedHostName kernel: platform eisa.0: Cannot allocate resource for EISA slot 5 Jul 27 14:42:41 undisclosedHostName kernel: platform eisa.0: Cannot allocate resource for EISA slot 6 Jul 27 14:42:41 undisclosedHostName kernel: platform eisa.0: Cannot allocate resource for EISA slot 7 Jul 27 14:42:41 undisclosedHostName kernel: platform eisa.0: Cannot allocate resource for EISA slot 8 -- 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/1837326 Title: platform eisa.0: EISA: Cannot allocate resource for mainboard Status in linux package in Ubuntu: Confirmed Bug description: dmesg: [0.889531] platform eisa.0: EISA: Cannot allocate resource for mainboard [0.889533] platform eisa.0: Cannot allocate resource for EISA slot 1 [0.889535] platform eisa.0: Cannot allocate resource for EISA slot 2 [0.889536] platform eisa.0: Cannot allocate resource for EISA slot 3 [0.889537] platform eisa.0: Cannot allocate resource for EISA slot 4 [0.889539] platform eisa.0: Cannot allocate resource for EISA slot 5 [0.889540] platform eisa.0: Cannot allocate resource for EISA slot 6 [0.889541] platform eisa.0: Cannot allocate resource for EISA slot 7 [0.889542] platform eisa.0: Cannot allocate resource for EISA slot 8 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.2.0-8-generic 5.2.0-8.9 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 ApportVersion: 2.20.11-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 3028 F pulseaudio /dev/snd/pcmC0D0p: caravena 3028 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jul 21 12:16:07 2019 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (230 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.2.0-8-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.2.0-8-generic N/A linux-backports-modules-5.2.0-8-generic N/A linux-firmware 1.181 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2018-12-02 (230 days ago) dmi.bios.date: 04/29/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.34 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP
[Kernel-packages] [Bug 1870994] Re: "*BAD*gran_size: 64K chunk_size: 32M num_reg: 10 lose cover RAM: -18M" in dmesg
See #6. ** 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/1870994 Title: "*BAD*gran_size: 64Kchunk_size: 32M num_reg: 10 lose cover RAM: -18M" in dmesg Status in linux package in Ubuntu: Confirmed Bug description: While looking at the attached dmesg which comes from an up-to-date eoan, I found certain lines containing *BAD* and "can not find optimal value", "please specify...". For me, they are just intimidating printfs. Should I get worried? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870994/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1870994] Re: "*BAD*gran_size: 64K chunk_size: 32M num_reg: 10 lose cover RAM: -18M" in dmesg
Provide me with a method to anonymize my data... ** Changed in: linux (Ubuntu) Status: Expired => New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1870994 Title: "*BAD*gran_size: 64Kchunk_size: 32M num_reg: 10 lose cover RAM: -18M" in dmesg Status in linux package in Ubuntu: Incomplete Bug description: While looking at the attached dmesg which comes from an up-to-date eoan, I found certain lines containing *BAD* and "can not find optimal value", "please specify...". For me, they are just intimidating printfs. Should I get worried? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870994/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1870994] Re: "*BAD*gran_size: 64K chunk_size: 32M num_reg: 10 lose cover RAM: -18M" in dmesg
@janitor I won't do "apport-collect ", since I do wish to anonymize my private data and the laptop data before it goes here. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1870994 Title: "*BAD*gran_size: 64Kchunk_size: 32M num_reg: 10 lose cover RAM: -18M" in dmesg Status in linux package in Ubuntu: Expired Bug description: While looking at the attached dmesg which comes from an up-to-date eoan, I found certain lines containing *BAD* and "can not find optimal value", "please specify...". For me, they are just intimidating printfs. Should I get worried? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870994/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1870995] Re: i8042: Warning: Keylock active
Alright; thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1870995 Title: i8042: Warning: Keylock active Status in linux package in Ubuntu: Incomplete Bug description: I see "i8042: Warning: Keylock active" in my dmesg. Since this is a warning, I get, ergo, warned. Well, about what do I get warned? I feel warned, but I don't know what's wrong and what do I have to avoid doing so that I don't get into trouble. Is there an issue there that needs to be solved? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870995/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1870995] Re: i8042: Warning: Keylock active
I don't even have PS/2 mouse/keyboard ports on the machine in question. They are only present on the docking station. If the computer is not plugged into the docking station, the warning still appears. If the computer is plugged into the docking station, USB keyboard and USB mouse are used. -- 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/1870995 Title: i8042: Warning: Keylock active Status in linux package in Ubuntu: Incomplete Bug description: I see "i8042: Warning: Keylock active" in my dmesg. Since this is a warning, I get, ergo, warned. Well, about what do I get warned? I feel warned, but I don't know what's wrong and what do I have to avoid doing so that I don't get into trouble. Is there an issue there that needs to be solved? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870995/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1870995] Re: i8042: Warning: Keylock active
If WHAT doesn't affect normal usage? As all computers, the computer in question suffers various issues of varying degree of severity from time to time, starting with (luckily, extremely seldom) shutting itsself off without warning and ending with dozens of warning printfs scattered over dozens of log files. -- 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/1870995 Title: i8042: Warning: Keylock active Status in linux package in Ubuntu: Incomplete Bug description: I see "i8042: Warning: Keylock active" in my dmesg. Since this is a warning, I get, ergo, warned. Well, about what do I get warned? I feel warned, but I don't know what's wrong and what do I have to avoid doing so that I don't get into trouble. Is there an issue there that needs to be solved? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870995/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1870994] Re: "*BAD*gran_size: 64K chunk_size: 32M num_reg: 10 lose cover RAM: -18M" in dmesg
** Description changed: - While looking at a dmesg on an up-to-date eoan, I found certain lines - containing *BAD* and "can not find optimal value", "please specify...". - For me, they are just intimidating printfs. Should I get worried? + While looking at the attached dmesg on an up-to-date eoan, I found + certain lines containing *BAD* and "can not find optimal value", "please + specify...". For me, they are just intimidating printfs. Should I get + worried? ** Description changed: - While looking at the attached dmesg on an up-to-date eoan, I found - certain lines containing *BAD* and "can not find optimal value", "please - specify...". For me, they are just intimidating printfs. Should I get - worried? + While looking at the attached dmesg which comes from an up-to-date eoan, + I found certain lines containing *BAD* and "can not find optimal value", + "please specify...". For me, they are just intimidating printfs. + Should I get worried? -- 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/1870994 Title: "*BAD*gran_size: 64Kchunk_size: 32M num_reg: 10 lose cover RAM: -18M" in dmesg Status in linux package in Ubuntu: Incomplete Bug description: While looking at the attached dmesg which comes from an up-to-date eoan, I found certain lines containing *BAD* and "can not find optimal value", "please specify...". For me, they are just intimidating printfs. Should I get worried? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870994/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1870994] Re: "*BAD*gran_size: 64K chunk_size: 32M num_reg: 10 lose cover RAM: -18M" in dmesg
@Ubuntu Kernel Bot: I won't do "apport-collect ", since I have to manually anonymize my private data and the laptop data before it goes here. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1870994 Title: "*BAD*gran_size: 64Kchunk_size: 32M num_reg: 10 lose cover RAM: -18M" in dmesg Status in linux package in Ubuntu: Incomplete Bug description: While looking at a dmesg on an up-to-date eoan, I found certain lines containing *BAD* and "can not find optimal value", "please specify...". For me, they are just intimidating printfs. Should I get worried? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870994/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1703964] Re: ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\PMIO) (20170119/utaddress-247)
Btw., the messages for me is slightly different as far as the numbers are concerned, e.g.: [0.556821] ACPI Warning: SystemIO range 0x1828-0x182F conflicts with OpRegion 0x1800-0x183F (\_SB.PCI0.EHC2.E1PM) (20190703/utaddress-204) -- 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/1703964 Title: ACPI Warning: SystemIO range 0x0428-0x042F conflicts with OpRegion 0x0400-0x047F (\PMIO) (20170119/utaddress-247) Status in linux package in Ubuntu: Confirmed Bug description: dmesg: [5.094986] ACPI Warning: SystemIO range 0x0428-0x042F conflicts with OpRegion 0x0400-0x047F (\PMIO) (20170119/utaddress-247) [5.094999] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [5.095003] ACPI Warning: SystemIO range 0x0540-0x054F conflicts with OpRegion 0x0500-0x0563 (\GPIO) (20170119/utaddress-247) [5.095012] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [5.095013] ACPI Warning: SystemIO range 0x0530-0x053F conflicts with OpRegion 0x0500-0x0563 (\GPIO) (20170119/utaddress-247) [5.095021] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [5.095023] ACPI Warning: SystemIO range 0x0500-0x052F conflicts with OpRegion 0x0500-0x0563 (\GPIO) (20170119/utaddress-247) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.11.0-10-generic 4.11.0-10.15 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 1464 F pulseaudio CurrentDesktop: GNOME Date: Wed Jul 12 15:43:43 2017 HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87 InstallationDate: Installed on 2017-07-05 (7 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-10-generic root=UUID=6b614287-8ce5-49c5-b66d-e92fa9568c2b ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.11.0-10-generic N/A linux-backports-modules-4.11.0-10-generic N/A linux-firmware 1.167 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-07-05 (6 days ago) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1703964/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1703964] Re: ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\PMIO) (20170119/utaddress-247)
Since the above is a warning, I feel, ergo, warned. But I don't know about what. I usually expect to get warned the following way: "If you do this and that, you run into such and such kind of trouble". Now, what is it that I get warned about in this case? I have various kinds of problems with the laptop from time to time (e.g., headset sometimes not working properly), but I have no idea which of the dozens error/warning messages might be related at all, if any. ** Attachment added: "dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1703964/+attachment/5347376/+files/dmesg.log ** Changed in: linux (Ubuntu) Status: Invalid => 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/1703964 Title: ACPI Warning: SystemIO range 0x0428-0x042F conflicts with OpRegion 0x0400-0x047F (\PMIO) (20170119/utaddress-247) Status in linux package in Ubuntu: Confirmed Bug description: dmesg: [5.094986] ACPI Warning: SystemIO range 0x0428-0x042F conflicts with OpRegion 0x0400-0x047F (\PMIO) (20170119/utaddress-247) [5.094999] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [5.095003] ACPI Warning: SystemIO range 0x0540-0x054F conflicts with OpRegion 0x0500-0x0563 (\GPIO) (20170119/utaddress-247) [5.095012] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [5.095013] ACPI Warning: SystemIO range 0x0530-0x053F conflicts with OpRegion 0x0500-0x0563 (\GPIO) (20170119/utaddress-247) [5.095021] ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver [5.095023] ACPI Warning: SystemIO range 0x0500-0x052F conflicts with OpRegion 0x0500-0x0563 (\GPIO) (20170119/utaddress-247) ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.11.0-10-generic 4.11.0-10.15 ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8 Uname: Linux 4.11.0-10-generic x86_64 ApportVersion: 2.20.5-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 1464 F pulseaudio CurrentDesktop: GNOME Date: Wed Jul 12 15:43:43 2017 HibernationDevice: RESUME=UUID=360bd2d2-4f44-4311-86d6-4781ac81ee87 InstallationDate: Installed on 2017-07-05 (7 days ago) InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.11.0-10-generic root=UUID=6b614287-8ce5-49c5-b66d-e92fa9568c2b ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.11.0-10-generic N/A linux-backports-modules-4.11.0-10-generic N/A linux-firmware 1.167 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-07-05 (6 days ago) dmi.bios.date: 04/15/2013 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P14AAJ dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: SAMSUNG_NP1234567890 dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP14AAJ:bd04/15/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.name: 530U3C/530U4C dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1703964/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1870994] [NEW] "*BAD*gran_size: 64K chunk_size: 32M num_reg: 10 lose cover RAM: -18M" in dmesg
Public bug reported: While looking at a dmesg on an up-to-date eoan, I found certain lines containing *BAD* and "can not find optimal value", "please specify...". For me, they are just intimidating printfs. Should I get worried? ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: eoan ** Attachment added: "dmesg.log" https://bugs.launchpad.net/bugs/1870994/+attachment/5347374/+files/dmesg.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/1870994 Title: "*BAD*gran_size: 64Kchunk_size: 32M num_reg: 10 lose cover RAM: -18M" in dmesg Status in linux package in Ubuntu: Incomplete Bug description: While looking at a dmesg on an up-to-date eoan, I found certain lines containing *BAD* and "can not find optimal value", "please specify...". For me, they are just intimidating printfs. Should I get worried? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870994/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
After "update-grub; update-initramfs -c -k all; update-grub" and a reboot, the message disappeared on the boot after the reboot. We'll see what happens next. -- 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: Confirmed 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. 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 1835660] Re: initramfs unpacking failed
Same message for me. The grub menu waits for at least 6 seconds, I think, instead of 0. I won't try anything crazy out before new package version(s) appears, as it is a production system, and I can't repair it in case booting fails. Attachment: the initial part of the dmesg log. ** Attachment added: "dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835660/+attachment/5347364/+files/dmesg.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/1835660 Title: initramfs unpacking failed Status in initramfs-tools package in Ubuntu: Confirmed 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. 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
