[Kernel-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu
Backporting to LTS is a good idea IMHO. A few additional use cases to consider - Users on the threshold who experience slight initrd image growth due to any module update - Users who thought they might be able to continue just using older images may fail to recognize grub will eventually remove those older images during regular updates. - Users that take their laptops on the road, but then plug them into their dock with larger displays to get the real work done only to have a boot failure. And yet when they take it into Best Buy it just works somehow. -- 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/1842320 Title: Can't boot: "error: out of memory." immediately after the grub menu Status in grub: Unknown Status in OEM Priority Project: Triaged Status in grub2-signed package in Ubuntu: Fix Committed Status in grub2-unsigned package in Ubuntu: Fix Released Status in initramfs-tools package in Ubuntu: Won't Fix Status in linux package in Ubuntu: Confirmed Bug description: [Workaround] Some workarounds have been suggested in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1842320/comments/125 [Impact] * In some cases, if the users’ initramfs grow bigger, then it’ll likely not be able to be loaded by grub2. * Some real cases from OEM projects: In many built-in 4k monitor laptops with nvidia drivers, the u-d-c puts the nvidia*.ko to initramfs which grows the initramfs to ~120M. Also the gfxpayload=auto will remain to use 4K resolution since it’s what EFI POST passed. In this case, the grub isn't able to load initramfs because the grub_memalign() won't be able to get suitable memory for the larger file: ``` #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376 #1 0x7dd7b074 in grub_malloc (size=592214020) at ../../../grub-core/kern/mm.c:408 #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076) at ../../../grub-core/kern/verifiers.c:150 #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 "/boot/initrd.img-5.17.0-1011-oem", type=131076) at ../../../grub-core/kern/file.c:121 #4 0x7bcd5a30 in ?? () #5 0x7fe21247 in ?? () #6 0x7bc030c8 in ?? () #7 0x00017fe21238 in ?? () #8 0x7bcd5320 in ?? () #9 0x7fe21250 in ?? () #10 0x in ?? () ``` Based on grub_mm_dump, we can see the memory region starvation in <1G addresses: Type StartEnd # Pages Attributes Available -00086FFF 0087 000F BS_Data00087000-00087FFF 0001 000F Available 00088000-0009EFFF 0017 000F Reserved 0009F000-0009 0001 000F Available 0010-00FF 0F00 000F LoaderCode 0100-01021FFF 0022 000F Available 01022000-238A7FFF 00022886 000F BS_Data238A8000-23927FFF 0080 000F Available 23928000-28860FFF 4F39 000F BS_Data28861000-2AB09FFF 22A9 000F LoaderCode 2AB0A000-2ACF8FFF 01EF 000F BS_Data2ACF9000-2B2FAFFF 0602 000F Available 2B2FB000-2B611FFF 0317 000F BS_Data2B612000-2B630FFF 001F 000F Available 2B631000-2B632FFF 0002 000F BS_Data2B633000-2B63CFFF 000A 000F Available 2B63D000-2B649FFF 000D 000F BS_Data2B64A000-2B64EFFF 0005 000F Available 2B64F000-2B666FFF 0018 000F BS_Data2B667000-2D8D5FFF 226F 000F LoaderCode 2D8D6000-2D8E9FFF 0014 000F BS_Data2D8EA000-2D925FFF 003C 000F LoaderCode 2D926000-2D932FFF 000D 000F BS_Data2D933000-2D969FFF 0037 000F BS_Code2D96A000-2D973FFF 000A 000F BS_Data2D974000-2E377FFF 0A04 000F Available 2E378000-2E37AFFF 0003 000F ... Reserved 3C08B000-4192 58A5 000F ACPI_NVS 4193-41B2 0200
[Kernel-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu
-> If an user somehow met this issue, then the system is not able to boot. It can boot, if it did previously, and this issue will get fixed pretty quick IMHO in the updates repository given it impacts current 20.04, 22.04 and 22.10. Here is just the workaround part, for current 22.10 or 22.04 to help people stuck on boot that used to have a working system. 1) Hold the SHIFT key on boot, and select the 2nd newest kernel from the advanced list in the grub menu: i.e. for myself, 5.19 broke, so using the older 5.15 allowed me to boot. 2) Open a terminal, sudo -i to root, and run these commands to download, install, and prevent upgrades to last version of initramfs-tools before the compression rates were changed, which allows you to regenerate your initrd image with the previously working smaller size. Download: wget https://ubuntu.repo.cure.edu.uy/mirror/pool/main/i/initramfs-tools/initramfs-tools-bin_0.140ubuntu12_amd64.deb wget https://ubuntu.repo.cure.edu.uy/mirror/pool/main/i/initramfs-tools/initramfs-tools-core_0.140ubuntu12_all.deb wget https://ubuntu.repo.cure.edu.uy/mirror/pool/main/i/initramfs-tools/initramfs-tools_0.140ubuntu12_all.deb Install: dpkg -i initramfs-tools-bin_0.140ubuntu12_amd64.deb dpkg -i initramfs-tools-core_0.140ubuntu12_all.deb dpkg -i initramfs-tools_0.140ubuntu12_all.deb Hold Upgrades: apt-mark hold initramfs-tools-bin apt-mark hold initramfs-tools-core apt-mark hold initramfs-tools Re-generate current initrd image: update-initramfs -u A reboot should just bring you up in 5.19. To restore the system to a normal state once the problem has been fixed in the current versions, unhold those same packages using the steps below, and the new ones will automatically be downloaded and installed. apt-mark unhold initramfs-tools-bin apt-mark unhold initramfs-tools-core apt-mark unhold initramfs-tools Some additional notes, not for the workaround above follow. Do NOT issue the "update-initramfs -k all" command, if you have been thinking about it as a first triage step. The reason being, if you have not applied some kind of fix or workaround prior, this will rebuild all your old previously working kernel initrd images with the new low compression directive, which might render them all unbootable, further complicating matters. If you get to this state, and you need a working live ISO, to chroot and fix, make sure to choose one prior with the older, increased initrd compresssion which must be 20.04.4 LTS or older. Current 20.05.5, and all 22.04 and 22.10 releases use the lower compression that can cause this issue and may not work. Impatient new installers may find this info useful as well. Another simpler workaround for more advanced users with 4K screens is to pass GFXMODE=640x480 in grub defaults and update-grub as mentioned here: http://savannah.gnu.org/bugs/?61058 -- 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/1842320 Title: Can't boot: "error: out of memory." immediately after the grub menu Status in grub: Unknown Status in OEM Priority Project: Triaged Status in grub2-signed package in Ubuntu: Triaged Status in grub2-unsigned package in Ubuntu: Triaged Status in initramfs-tools package in Ubuntu: Won't Fix Status in linux package in Ubuntu: Confirmed Bug description: [Impact] * In some cases, if the users’ initramfs grow bigger, then it’ll likely not be able to be loaded by grub2. * Some real cases from OEM projects: In many built-in 4k monitor laptops with nvidia drivers, the u-d-c puts the nvidia*.ko to initramfs which grows the initramfs to ~120M. Also the gfxpayload=auto will remain to use 4K resolution since it’s what EFI POST passed. In this case, the grub isn't able to load initramfs because the grub_memalign() won't be able to get suitable memory for the larger file: ``` #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376 #1 0x7dd7b074 in grub_malloc (size=592214020) at ../../../grub-core/kern/mm.c:408 #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076) at ../../../grub-core/kern/verifiers.c:150 #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 "/boot/initrd.img-5.17.0-1011-oem", type=131076) at ../../../grub-core/kern/file.c:121 #4 0x7bcd5a30 in ?? () #5 0x7fe21247 in ?? () #6 0x7bc030c8 in ?? () #7 0x00017fe21238 in ?? () #8 0x7bcd5320 in ?? () #9 0x7fe21250 in ?? () #10 0x in ?? () ``` Based on grub_mm_dump, we can see the memory fragment (some parts seem likely be used because of 4K resolution?) and doesn’t have available contiguous memory for larger file as: ``` grub_real_malloc(...) ... if (cur->size >= n + extra) ``` Based on UEFI Specification Section 7.2[1] and UEFI driver writers’ guide 4.2.3[2], we
[Kernel-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu
My XPS 13 9380 (no luks) also triggers this on 5.19 after the 22.10 upgrade; I can see the initrd is about 7% bigger in 22.10 over 22.04. -rw-r--r-- 1 root root 111203941 Oct 30 18:16 initrd.img-5.15.0-52-generic -rw-r--r-- 1 root root 120222346 Oct 31 21:39 initrd.img-5.19.0-23-generic #103 lays out some interesting blockers for grub2, so as of right now there is no simple way to get upstream through ubuntu repositories as grub2 2.06-2ubuntu12 does not have a fix. I think it is interesting that in https://lists.gnu.org/archive/html/grub-devel/2017-03/msg00037.html there was pushback on autodetection to fix this, citing "that machine that nobody heard of that will fail" however it ended up being a bunch of not-yet-built systems that failed Looking at initramfs-tools in Jammy, the very last changelog entry was the change to lower compression, that is triggering this issue: http://changelogs.ubuntu.com/changelogs/pool/main/i/initramfs- tools/initramfs-tools_0.140ubuntu13/changelog initramfs-tools (0.140ubuntu13) jammy; urgency=medium * Lower the compression levels for zstd and lz4 (LP: #1958148) Following the discussion on the mailing list, we have reached a conclusion to lower the default compression levels: - For lz4, the compression level is lowered to 2 from 9 - For zstd, the compression level is lowered to 1 from 19 Simple fix IMHO is to just go back one version. Ubuntu main archive doesn't include all old versions, but other mirrors do. Here are some quick steps that let you run official binaries from Jammy under Kinetic to work around this issue until grub2 catches up and/or they tweak compression, or make compression more easily tunable. wget https://ubuntu.repo.cure.edu.uy/mirror/pool/main/i/initramfs-tools/initramfs-tools-bin_0.140ubuntu12_amd64.deb wget https://ubuntu.repo.cure.edu.uy/mirror/pool/main/i/initramfs-tools/initramfs-tools-core_0.140ubuntu12_all.deb wget https://ubuntu.repo.cure.edu.uy/mirror/pool/main/i/initramfs-tools/initramfs-tools_0.140ubuntu12_all.deb dpkg -i initramfs-tools-bin_0.140ubuntu12_amd64.deb dpkg -i initramfs-tools-core_0.140ubuntu12_all.deb dpkg -i initramfs-tools_0.140ubuntu12_all.deb apt-mark hold initramfs-tools-bin apt-mark hold initramfs-tools-core apt-mark hold initramfs-tools update-initramfs -u Afterwards, big drop in initrd size. -rw-r--r-- 1 root root 111203941 Oct 30 18:16 initrd.img-5.15.0-52-generic -rw-r--r-- 1 root root 79034965 Oct 31 22:50 initrd.img-5.19.0-23-generic Sometime down the road, when this bug is closed, you will want to un- hold these to restore the lastest packages apt-mark unhold initramfs-tools-bin apt-mark unhold initramfs-tools-core apt-mark unhold initramfs-tools -- 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/1842320 Title: Can't boot: "error: out of memory." immediately after the grub menu Status in grub: Unknown Status in OEM Priority Project: Triaged Status in grub2-signed package in Ubuntu: Triaged Status in grub2-unsigned package in Ubuntu: Triaged Status in initramfs-tools package in Ubuntu: Won't Fix Status in linux package in Ubuntu: Confirmed Bug description: [Impact] * In some cases, if the users’ initramfs grow bigger, then it’ll likely not be able to be loaded by grub2. * Some real cases from OEM projects: In many built-in 4k monitor laptops with nvidia drivers, the u-d-c puts the nvidia*.ko to initramfs which grows the initramfs to ~120M. Also the gfxpayload=auto will remain to use 4K resolution since it’s what EFI POST passed. In this case, the grub isn't able to load initramfs because the grub_memalign() won't be able to get suitable memory for the larger file: ``` #0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376 #1 0x7dd7b074 in grub_malloc (size=592214020) at ../../../grub-core/kern/mm.c:408 #2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076) at ../../../grub-core/kern/verifiers.c:150 #3 0x7dd801d4 in grub_file_open (name=0x7bc02f00 "/boot/initrd.img-5.17.0-1011-oem", type=131076) at ../../../grub-core/kern/file.c:121 #4 0x7bcd5a30 in ?? () #5 0x7fe21247 in ?? () #6 0x7bc030c8 in ?? () #7 0x00017fe21238 in ?? () #8 0x7bcd5320 in ?? () #9 0x7fe21250 in ?? () #10 0x in ?? () ``` Based on grub_mm_dump, we can see the memory fragment (some parts seem likely be used because of 4K resolution?) and doesn’t have available contiguous memory for larger file as: ``` grub_real_malloc(...) ... if (cur->size >= n + extra) ``` Based on UEFI Specification Section 7.2[1] and UEFI driver writers’ guide 4.2.3[2], we can ask 32bits+ on AllocatePages(). As most X86_64 platforms should support 64 bits addressing, we should extend GRUB_EFI_MAX_
[Kernel-packages] [Bug 1882510] Re: IRQ/51-SYNA2393 using lots of CPU after suspend/resume
In my case, I am running Ubuntu 22.04 uptodate. This trackpad bug has been around a while, and due to the slight process naming differences between platforms, it can be hard to link them together. For myself, this happens on my XPS 13 9385, after coming out of sleep, with a similarly named process irq/51-DELL08AF It has been reported on other, much older platforms, such as https://bugzilla.redhat.com/show_bug.cgi?id=1656416 Notably it lives the life of the OS version and gets closed every time. Seems like a kernel bug that is persistent over different distributions and versions going back to at least 2018. Thanks to this post, where I figured out the workaround https://www.dell.com/community/Precision-Mobile-Workstations/High-load- heating-up-fan-noise-after-S3-suspend-and-resume-on/td-p/7441933 In some instances, the workaround was not discovered https://gitlab.freedesktop.org/libinput/libinput/-/issues/263 My hardware is 06cb:76af, but seems like the issue is likely with the driver/kernel/sleep interaction than any specific hardware model from my quick googling. # dmesg | grep -i touchpad [1.381426] input: DELL08AF:00 06CB:76AF Touchpad as /devices/pci:00/:00:15.1/i2c_designware.1/i2c-1/i2c-DELL08AF:00/0018:06CB:76AF.0002/input/input11 [8.205524] input: DELL08AF:00 06CB:76AF Touchpad as /devices/pci:00/:00:15.1/i2c_designware.1/i2c-1/i2c-DELL08AF:00/0018:06CB:76AF.0002/input/input37 ** Bug watch added: Red Hat Bugzilla #1656416 https://bugzilla.redhat.com/show_bug.cgi?id=1656416 ** Bug watch added: gitlab.freedesktop.org/libinput/libinput/-/issues #263 https://gitlab.freedesktop.org/libinput/libinput/-/issues/263 -- 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/1882510 Title: IRQ/51-SYNA2393 using lots of CPU after suspend/resume Status in linux package in Ubuntu: Confirmed Bug description: After a suspend/resume cycle (using "deep" suspend mode), the process IRQ/51-SYNA2393 uses considerable CPU 10+%. Using the trackpad for a few seconds seems to fix the issue. I don't normally use the trackpad while docked so it's a bit annoying to have to remember to use it just to get this problem to go away. Looks like others have hit the same issue; I found this on askubuntu: https://askubuntu.com/questions/1138642/ubuntu-18-04-drains-battery- very-fast-after-wake-up-from-a-deep-sleep ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-generic 5.4.0.33.38 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shaun 2997 F pulseaudio /dev/snd/controlC0: shaun 2997 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 8 11:30:07 2020 InstallationDate: Installed on 2018-12-11 (544 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: Dell Inc. Precision 5530 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-33-generic root=/dev/mapper/ubuntu--vg-root ro mem_sleep_default=deep resume=/dev/disk/by-uuid/01f98d09-5f44-4469-904b-c976fbd46d96 quiet splash RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-02 (36 days ago) dmi.bios.date: 12/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0FP2W2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd12/25/2019:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0FP2W2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882510/+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 1595765] Re: Wifi drivers all fail to build [error: ‘IEEE80211_BAND_2GHZ’ undeclared here]
Can the maintainers please have a look at the following for rtl8812au 4.3.20, https://github.com/diederikdehaas/rtl8812AU/tree/driver-4.3.20 It is working on my Ubuntu 16.10 and resolves the build issues with the current 4.3.14 dkms source. root@dottodesk:/usr/src# uname -a Linux dottodesk 4.8.0-42-generic #45-Ubuntu SMP Wed Mar 8 20:06:06 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux My device works fine with a quick root@dottodesk:/usr/src# modprobe cfg80211 root@dottodesk:/usr/src# modprobe 8812au [427821.372227] RTL871X: module init start [427821.372228] RTL871X: rtl8812au v4.3.20_16317.20160108 [427821.458209] RTL871X: rtw_ndev_init(wlan0) if1 mac_addr=24:05:0f:9e:83:76 [427821.458411] usbcore: registered new interface driver rtl8812au [427821.458412] RTL871X: module init ret=0 [427821.462679] rtl8812au 3-12:1.0 wlx24050f9e8376: renamed from wlan0 [427821.530598] IPv6: ADDRCONF(NETDEV_UP): wlx24050f9e8376: link is not ready [427821.917526] IPv6: ADDRCONF(NETDEV_UP): wlx24050f9e8376: link is not ready [427821.969946] IPv6: ADDRCONF(NETDEV_UP): wlx24050f9e8376: link is not ready [427824.223886] RTL871X: nolinked power save enter [427824.629043] RTL871X: nolinked power save leave [427826.880306] RTL871X: rtw_set_802_11_connect(wlx24050f9e8376) fw_state=0x0008 [427835.590301] RTL871X: rtw_set_802_11_connect(wlx24050f9e8376) fw_state=0x0008 [427837.807465] RTL871X: start auth [427837.810252] RTL871X: auth success, start assoc [427837.812764] RTL871X: rtw_cfg80211_indicate_connect(wlx24050f9e8376) BSS not found !! [427837.812777] RTL871X: assoc success [427837.813382] IPv6: ADDRCONF(NETDEV_CHANGE): wlx24050f9e8376: link becomes ready [427837.815506] RTL871X: recv eapol packet [427837.815623] RTL871X: send eapol packet [427837.818466] RTL871X: recv eapol packet [427837.818535] RTL871X: send eapol packet [427837.818967] RTL871X: set pairwise key camid:4, addr:60:e3:27:2f:16:30, kid:0, type:AES [427837.819803] RTL871X: set group key camid:5, addr:60:e3:27:2f:16:30, kid:1, type:AES [427863.277967] RTL871X: recv eapol packet [427863.278232] RTL871X: set group key camid:6, addr:60:e3:27:2f:16:30, kid:2, type:AES [427863.278234] RTL871X: send eapol packet [427950.466209] RTL871X: nolinked power save enter [427951.404732] RTL871X: nolinked power save leave [427953.674222] RTL871X: nolinked power save enter [427974.412409] RTL871X: nolinked power save leave [427976.673020] RTL871X: nolinked power save enter [428007.414333] RTL871X: nolinked power save leave [428009.678280] RTL871X: nolinked power save enter [428050.444797] RTL871X: nolinked power save leave [428052.706589] RTL871X: nolinked power save enter root@dottodesk:/usr/src# dkms status rtl8812AU, 4.3.20, 4.8.0-42-generic, x86_64: installed rtl8812au, 4.3.8.12175.20140902+dfsg: added -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1595765 Title: Wifi drivers all fail to build [error: ‘IEEE80211_BAND_2GHZ’ undeclared here] Status in bcmwl package in Ubuntu: Confirmed Status in broadcom-sta package in Ubuntu: Confirmed Status in rtl8812au package in Ubuntu: Confirmed Bug description: error update for kernel 4.7 RC 3 ProblemType: Package DistroRelease: elementary 0.4 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8 [origin: Ubuntu] Uname: Linux 4.6.2-040602-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 DKMSKernelVersion: 4.7.0-040700rc3-generic Date: Thu Jun 23 22:03:59 2016 DuplicateSignature: dkms:bcmwl-kernel-source:6.30.223.248+bdcom-0ubuntu8:/var/lib/dkms/bcmwl/6.30.223.248+bdcom/build/src/wl/sys/wl_cfg80211_hybrid.c:237:12: error: ‘IEEE80211_BAND_2GHZ’ undeclared here (not in a function) InstallationDate: Installed on 2016-06-14 (9 days ago) InstallationMedia: elementary OS 0.4 "Loki" - Daily amd64 (20160613) PackageVersion: 6.30.223.248+bdcom-0ubuntu8 RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: bcmwl Title: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu8: bcmwl kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1595765/+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 1089768] Re: Marvell Sata controller and AMD-Vi problems
Updated here https://lkml.org/lkml/2014/5/22/685 -- 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/1089768 Title: Marvell Sata controller and AMD-Vi problems Status in linux package in Ubuntu: Expired Bug description: This bug is to confirm that the Marvell 88SE9128 chipset bug presents under AMD's IOMMU implementation as well as Intel's VT-D. I've tested this with a Syba SD-PEX40035 and a Highpoint Rocket 620 (both use the same Marvell chipset) PCIe card, under both the stock Quantal kernel and the 3.7.0rc8 kernel from the mainline kernel PPA. It sounds like the preferred solution is PCI quirk, and some of the infrastructure is in place, but it hasn't been implemented yet. Symptoms consist of a much longer boot process, and failure to identify any devices attached to the Marvell controllers. WORKAROUND: Works fine as long as I disable the IOMMU in the BIOS. My system consists of an AMD A10-5800K in a Gigabyte GA-F2A85X-D3H motherboard, 5x Seagate 1.5 TB drives in software Raid5, 4x Seagate 3 TB drives in a native ZFS raidz (not yet used), a Sata BD-ROM, and a 500 GB sata drive (not yet used). https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1005226 http://lists.linuxfoundation.org/pipermail/iommu/2012-September/004551.html https://bugzilla.kernel.org/show_bug.cgi?id=42679 https://bugzilla.redhat.com/show_bug.cgi?id=757166 pci 02:00.1 is the IDE endpoint, but there are no PATA devices in the system, which matches the behavior of the other chips (emitting DMA operations from the wrong PCI endpoint, which the IOMMU rejects.) ## 02:00.1 IDE interface: Marvell Technology Group Ltd. 88SE9128 IDE Controller (rev 11) (prog-if 8f [Master SecP SecO PriP PriO]) Subsystem: Marvell Technology Group Ltd. 88SE9128 IDE Controller Flags: bus master, fast devsel, latency 0, IRQ 18 I/O ports at d040 [size=8] I/O ports at d030 [size=4] I/O ports at d020 [size=8] I/O ports at d010 [size=4] I/O ports at d000 [size=16] Memory at fea2 (32-bit, non-prefetchable) [size=16] Expansion ROM at fea0 [disabled] [size=64K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit- Capabilities: [70] Express Legacy Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Kernel driver in use: pata_marvell Kernel modules: pata_marvell ## [1.225703] AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.1 domain=0x001d address=0x001003c0 flags=0x] [6.207818] ata16.00: qc timeout (cmd 0xa1) [6.215674] ata9.00: qc timeout (cmd 0xa1) [6.215681] ata9.00: failed to IDENTIFY (I/O error, err_mask=0x4) [6.223640] ata24.00: qc timeout (cmd 0xa1) [6.231606] ata17.00: qc timeout (cmd 0xec) [6.231627] ata24.00: failed to IDENTIFY (I/O error, err_mask=0x4) [6.239574] ata17.00: failed to IDENTIFY (I/O error, err_mask=0x4) [6.343207] ata18.00: qc timeout (cmd 0xec) [6.351204] ata18.00: failed to IDENTIFY (I/O error, err_mask=0x4) [6.534578] ata9: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [6.558489] ata24: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [6.709935] ata16.00: failed to IDENTIFY (I/O error, err_mask=0x4) [7.531002] ata16: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 11.588451] ata17: link is slow to respond, please be patient (ready=0) [ 11.700054] ata18: link is slow to respond, please be patient (ready=0) [ 16.219859] ata17: COMRESET failed (errno=-16) [ 16.331454] ata18: COMRESET failed (errno=-16) [ 16.498853] ata9.00: qc timeout (cmd 0xa1) [ 16.498865] ata9.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 16.498870] ata9: limiting SATA link speed to 1.5 Gbps [ 16.522792] ata24.00: qc timeout (cmd 0xa1) [ 16.522804] ata24.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 16.522807] ata24: limiting SATA link speed to 1.5 Gbps [ 16.817725] ata9: SATA link up 1.5 Gbps (SStatus 113 SControl 310) [ 16.849613] ata24: SATA link up 1.5 Gbps (SStatus 113 SControl 310) [ 17.495260] ata16.00: qc timeout (cmd 0xa1) [ 17.997499] ata16.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 17.997504] ata16: limiting SATA link speed to 1.5 Gbps [ 18.818556] ata16: SATA link up 1.5 Gbps (SStatus 113 SControl 310) [ 21.568700] ata17: link is slow to respond, please be patient (ready=0) [ 21.680300] ata18: link is slow to respond, please be patient (ready=0) [ 26.200104] ata17: COMRESET failed (errno=-16) [ 26.311693] ata18: COMRESET failed (errno=-16) [ 31.548931] ata17: link is slow
[Kernel-packages] [Bug 1089768] Re: Marvell Sata controller and AMD-Vi problems
Looks like there is a patch here: https://lkml.org/lkml/2013/3/7/582 -- 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/1089768 Title: Marvell Sata controller and AMD-Vi problems Status in linux package in Ubuntu: Expired Bug description: This bug is to confirm that the Marvell 88SE9128 chipset bug presents under AMD's IOMMU implementation as well as Intel's VT-D. I've tested this with a Syba SD-PEX40035 and a Highpoint Rocket 620 (both use the same Marvell chipset) PCIe card, under both the stock Quantal kernel and the 3.7.0rc8 kernel from the mainline kernel PPA. It sounds like the preferred solution is PCI quirk, and some of the infrastructure is in place, but it hasn't been implemented yet. Symptoms consist of a much longer boot process, and failure to identify any devices attached to the Marvell controllers. WORKAROUND: Works fine as long as I disable the IOMMU in the BIOS. My system consists of an AMD A10-5800K in a Gigabyte GA-F2A85X-D3H motherboard, 5x Seagate 1.5 TB drives in software Raid5, 4x Seagate 3 TB drives in a native ZFS raidz (not yet used), a Sata BD-ROM, and a 500 GB sata drive (not yet used). https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1005226 http://lists.linuxfoundation.org/pipermail/iommu/2012-September/004551.html https://bugzilla.kernel.org/show_bug.cgi?id=42679 https://bugzilla.redhat.com/show_bug.cgi?id=757166 pci 02:00.1 is the IDE endpoint, but there are no PATA devices in the system, which matches the behavior of the other chips (emitting DMA operations from the wrong PCI endpoint, which the IOMMU rejects.) ## 02:00.1 IDE interface: Marvell Technology Group Ltd. 88SE9128 IDE Controller (rev 11) (prog-if 8f [Master SecP SecO PriP PriO]) Subsystem: Marvell Technology Group Ltd. 88SE9128 IDE Controller Flags: bus master, fast devsel, latency 0, IRQ 18 I/O ports at d040 [size=8] I/O ports at d030 [size=4] I/O ports at d020 [size=8] I/O ports at d010 [size=4] I/O ports at d000 [size=16] Memory at fea2 (32-bit, non-prefetchable) [size=16] Expansion ROM at fea0 [disabled] [size=64K] Capabilities: [40] Power Management version 3 Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit- Capabilities: [70] Express Legacy Endpoint, MSI 00 Capabilities: [100] Advanced Error Reporting Kernel driver in use: pata_marvell Kernel modules: pata_marvell ## [1.225703] AMD-Vi: Event logged [IO_PAGE_FAULT device=02:00.1 domain=0x001d address=0x001003c0 flags=0x] [6.207818] ata16.00: qc timeout (cmd 0xa1) [6.215674] ata9.00: qc timeout (cmd 0xa1) [6.215681] ata9.00: failed to IDENTIFY (I/O error, err_mask=0x4) [6.223640] ata24.00: qc timeout (cmd 0xa1) [6.231606] ata17.00: qc timeout (cmd 0xec) [6.231627] ata24.00: failed to IDENTIFY (I/O error, err_mask=0x4) [6.239574] ata17.00: failed to IDENTIFY (I/O error, err_mask=0x4) [6.343207] ata18.00: qc timeout (cmd 0xec) [6.351204] ata18.00: failed to IDENTIFY (I/O error, err_mask=0x4) [6.534578] ata9: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [6.558489] ata24: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [6.709935] ata16.00: failed to IDENTIFY (I/O error, err_mask=0x4) [7.531002] ata16: SATA link up 1.5 Gbps (SStatus 113 SControl 300) [ 11.588451] ata17: link is slow to respond, please be patient (ready=0) [ 11.700054] ata18: link is slow to respond, please be patient (ready=0) [ 16.219859] ata17: COMRESET failed (errno=-16) [ 16.331454] ata18: COMRESET failed (errno=-16) [ 16.498853] ata9.00: qc timeout (cmd 0xa1) [ 16.498865] ata9.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 16.498870] ata9: limiting SATA link speed to 1.5 Gbps [ 16.522792] ata24.00: qc timeout (cmd 0xa1) [ 16.522804] ata24.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 16.522807] ata24: limiting SATA link speed to 1.5 Gbps [ 16.817725] ata9: SATA link up 1.5 Gbps (SStatus 113 SControl 310) [ 16.849613] ata24: SATA link up 1.5 Gbps (SStatus 113 SControl 310) [ 17.495260] ata16.00: qc timeout (cmd 0xa1) [ 17.997499] ata16.00: failed to IDENTIFY (I/O error, err_mask=0x4) [ 17.997504] ata16: limiting SATA link speed to 1.5 Gbps [ 18.818556] ata16: SATA link up 1.5 Gbps (SStatus 113 SControl 310) [ 21.568700] ata17: link is slow to respond, please be patient (ready=0) [ 21.680300] ata18: link is slow to respond, please be patient (ready=0) [ 26.200104] ata17: COMRESET failed (errno=-16) [ 26.311693] ata18: COMRESET failed (errno=-16) [ 31.548931]
[Kernel-packages] [Bug 1242272] Re: [HP EliteBook 8560w] Bluetooth does not work on ubuntu 13.10
Launchpad isn't allowing me to add my details to this report, but I don't another bug (assuming this is a duplicate) and it is set to expire in 4 days. The broadcom USB device is not even showing up in lsusb. It is detected and then disconnects. Since it used to work previously I am hesitant to upgrade my BIOS (as suggested by somebody) as HP conveniently disabled the CPU Turbo Mode in the newest BIOS due to some overheating issues (which are manageable, and I like to have the extra horsepower at my disposal). I also see no evidence that the BIOS upgrade changes the situation. Here is the attempt by system to load the btusb driver when enabling Bluetooth. [ 1636.198732] usbcore: registered new interface driver btusb [ 1636.478909] usb 2-1.6: USB disconnect, device number 4 [ 1644.603424] usb 2-1.6: new full-speed USB device number 5 using ehci-pci [ 1644.700177] usb 2-1.6: New USB device found, idVendor=03f0, idProduct=231d [ 1644.700188] usb 2-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 1644.700195] usb 2-1.6: Product: HP Integrated Module [ 1644.700200] usb 2-1.6: Manufacturer: Broadcom Corp [ 1644.917890] usb 2-1.6: USB disconnect, device number 5 [ 1645.092461] systemd-udevd[4661]: Failed to apply ACL on /dev/bus/usb/002/005: No such file or directory The udev ACL fails because the device is already gone; Nowhere in lsusb either. imac@imachp:~$ lsusb Bus 002 Device 003: ID 1bcf:2805 Sunplus Innovation Technology Inc. Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 001 Device 003: ID 138a:003c Validity Sensors, Inc. VFS471 Fingerprint Reader Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub -- 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/1242272 Title: [HP EliteBook 8560w] Bluetooth does not work on ubuntu 13.10 Status in “linux” package in Ubuntu: Incomplete Bug description: HP EliteBook 8560w, Ubuntu 13.10 (no any problem in 13.04) cat /proc/version_signature Ubuntu 3.11.0-12.19-generic 3.11.3 dmesg | grep -i bluetooth [ 10.744171] Bluetooth: Core ver 2.16 [ 10.744190] Bluetooth: HCI device and connection manager initialized [ 10.744198] Bluetooth: HCI socket layer initialized [ 10.744203] Bluetooth: L2CAP socket layer initialized [ 10.744209] Bluetooth: SCO socket layer initialized [ 10.750931] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 10.750935] Bluetooth: BNEP filters: protocol multicast [ 10.750945] Bluetooth: BNEP socket layer initialized [ 10.751432] Bluetooth: RFCOMM TTY layer initialized [ 10.751441] Bluetooth: RFCOMM socket layer initialized [ 10.751442] Bluetooth: RFCOMM ver 1.11 Trying to switch on bluetooth in System settings/Bluetooth - sudo tail -f /var/log/syslog Oct 20 10:46:58 max-8560w kernel: [ 1351.004248] usb 2-1.6: new full-speed USB device number 13 using ehci-pci Oct 20 10:46:58 max-8560w kernel: [ 1351.100829] usb 2-1.6: New USB device found, idVendor=03f0, idProduct=231d Oct 20 10:46:58 max-8560w kernel: [ 1351.100841] usb 2-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=0 Oct 20 10:46:58 max-8560w kernel: [ 1351.100847] usb 2-1.6: Product: HP Integrated Module Oct 20 10:46:58 max-8560w kernel: [ 1351.100852] usb 2-1.6: Manufacturer: Broadcom Corp Oct 20 10:46:58 max-8560w logger: loading HP Device 002 013 Oct 20 10:46:58 max-8560w bluetoothd[516]: Unknown command complete for opcode 19 Oct 20 10:46:58 max-8560w bluetoothd[516]: Endpoint registered: sender=:1.64 path=/MediaEndpoint/HFPAG Oct 20 10:46:58 max-8560w bluetoothd[516]: Endpoint registered: sender=:1.64 path=/MediaEndpoint/HFPHS Oct 20 10:46:58 max-8560w bluetoothd[516]: Endpoint registered: sender=:1.64 path=/MediaEndpoint/A2DPSource Oct 20 10:46:58 max-8560w bluetoothd[516]: Endpoint registered: sender=:1.64 path=/MediaEndpoint/A2DPSink Oct 20 10:46:58 max-8560w bluetoothd[516]: Adapter /org/bluez/516/hci0 has been enabled Oct 20 10:46:59 max-8560w bluetoothd[516]: Adapter /org/bluez/516/hci0 has been disabled Oct 20 10:46:59 max-8560w bluetoothd[516]: Unregister path: /org/bluez/516/hci0 Oct 20 10:46:59 max-8560w bluetoothd[516]: Endpoint unregistered: sender=:1.64 path=/MediaEndpoint/A2DPSink Oct 20 10:46:59 max-8560w bluetoothd[516]: Endpoint unregistered: sender=:1.64 path=/MediaEndpoint/A2DPSource Oct 20 10:46:59 max-8560w bluetoothd[516]: Endpoint unregistered: sender=:1.64 path=/MediaEndpoint/HFPAG Oct 20 10:46:59 max-8560w bluetoothd[516]: Endpoint unregistered: sender=:1.64 path=/MediaEndpoint/HFPHS Oct 20 10:46:59
[Kernel-packages] [Bug 1256923] [NEW] LuksOpen failed on boot after kernel upgrade
Public bug reported: immediately following an upgrade to 3.11.0-14.21(saucy/proposed) it appeared that the AES module required to unlock my luks encrypted volume for /home was not available on boot. It was strange, as I had executed apt-get upgrade, but when I returned to my console minutes later, the system appeared to have rebooted and was prompting (as it normally would on boot) for my passphrase to unlock my home directory. The console, on boot, displayed an 'unknown type' after authentication for crypt_luks, and the console option (Skip or Manual) was only presented and available very briefly after the first authentication prompt. Even with valid credentials, subsequent re-prompts appeared and failed with the same error. After another reboot, I authenticated, quickly hit M (to break into conole) and was able to get into the console with a working system with partitions (/, var, etc) mounted except that /boot was not mounted and my encrypted /home was not mounted. I was able to mount boot (giving me access to grub.conf), but was unable to unlock my crypted home directory using cryptsetup from the command line. cryptysetup luksopen did however complain the module for AES was not loaded. Modprobe did not find the module requested. I didn't waste too much more time as I need this system for work, and quickly just replaced 3.11.0-14 with 3.11.0-13 in my grub.conf and I was back up and running after a reboot. A quick check on apt after the reboot revealed no half-installed kernels or packages of any kind (which was my first guess as to root cause). If I get some time later this week, I may try and reinstall the latest kernel to capture more info. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: linux-image-3.11.0-14-generic 3.11.0-14.21 ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6 Uname: Linux 3.11.0-13-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: imac 2900 F pulseaudio /dev/snd/controlC0: imac 2900 F pulseaudio /dev/snd/pcmC0D0p: imac 2900 F...m pulseaudio CRDA: Error: [Errno 2] No such file or directory: 'iw' Date: Mon Dec 2 08:10:34 2013 HibernationDevice: RESUME=UUID=3b6a4263-a010-4ccd-ac16-6ad710af56f9 MachineType: Hewlett-Packard HP EliteBook 8560w MarkForUpload: True ProcEnviron: LANGUAGE=en_US:en TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-13-generic root=/dev/mapper/hostname-root ro nouveau.modeset=0 quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.11.0-13-generic N/A linux-backports-modules-3.11.0-13-generic N/A linux-firmware 1.116 SourcePackage: linux UpgradeStatus: Upgraded to saucy on 2013-09-07 (85 days ago) dmi.bios.date: 07/25/2011 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68SVD Ver. F.03 dmi.board.name: 1631 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 01.35 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68SVDVer.F.03:bd07/25/2011:svnHewlett-Packard:pnHPEliteBook8560w:pvrA0001D02:rvnHewlett-Packard:rn1631:rvrKBCVersion01.35:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 8560w dmi.product.version: A0001D02 dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug package-from-proposed saucy ** Description changed: immediately following an upgrade to 3.11.0-14.21(saucy/proposed) it appeared that the AES module required to unlock my luks encrypted volume for /home was not available on boot. - It was strange, as I had execute apt-get upgrade, but when I returned + It was strange, as I had executed apt-get upgrade, but when I returned to my console minutes later, the system appeared to have rebooted and was prompting (as it normally would on boot) for my passphrase to unlock my home directory. The console, on boot, displayed an 'unknown type' after authentication for crypt_luks, and the console option (Skip or Manual) was only presented and available very briefly after the first authentication prompt. Even with valid credentials, subsequent re-prompts appeared and failed with the same error. After another reboot, I authenticated, quickly hit M (to break into conole) and was able to get into the console with a working system with partitions (/, var, etc) mounted except that /boot was not mounted and my encrypted /home was not mounted. I was able to mount boot (giving me access to grub.conf), but was unable to unlock my crypted home directory using cryptsetup from the comman
