Ok, sorry for that. I was mislead by the kernel bot messages and the latest
comments.
The macbook failure is btw. caused by a change mentioned in #4 "- SAUCE: hack:
efi/libstub: mitigate t14s exit_boot_services() failure" which is currently
preventing the plucky kernel and isos from booting on
-propose kernel linux-hwe-6.14/6.14.0-22.22~24.04.1 still fails to boot
on older macbook.
** Tags removed: verification-needed-noble-linux-hwe-6.14
** Tags added: verification-failed-noble-linux-hwe-6.14
--
You received this bug notification because you are a member of Kernel
Packages, which is
Eric, this here is the offending commit:
https://git.launchpad.net/~ubuntu-
kernel/ubuntu/+source/linux/+git/plucky/commit/drivers/firmware/efi?h=master-
next&id=524da2cfa3da1c60e90db958e33402f4e070c916
I guess that Apples EFI implementation isn't perfect, so these changes
may work on regular PCs
** Patch added: "this is the problematic patch which I had reverted to make my
macbook 8,1 boot again"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2105402/+attachment/5875870/+files/libstub.patch
--
You received this bug notification because you are a member of Kernel
Packages, whic
I can confirm that this patch was the culprit. Please revert as it seems
not to fix the original problem it was made for anyway:
https://lore.kernel.org/linux-arm-
msm/z1hhatacgivaj...@hovoldconsulting.com/
--
You received this bug notification because you are a member of Kernel
Packages, which i
seems to be fixed in linux-image-6.5.0-16-generic (frpm kernel ppa).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.5 in Ubuntu.
https://bugs.launchpad.net/bugs/2037214
Title:
evict_inodes inode xxx, i_count = 1, was skippe
*** This bug is a duplicate of bug 2037214 ***
https://bugs.launchpad.net/bugs/2037214
** This bug has been marked a duplicate of bug 2037214
evict_inodes inode xxx, i_count = 1, was skipped!
--
You received this bug notification because you are a member of Kernel
Packages, which is subsc
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
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/1783746
Title:
ipmmu is always registered
Status in li
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
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/1787945
Title:
Tango platform uses __initcall without f
well, I think you forgot to attach the patch. So I called editconfig
myself and disabled the TANGO platform. For unknown reasons, this also
enables CONFIG_ARCH_HAS_FILTER_PGPROT in config.common.ubuntu... Anyway,
the new kernel boots and suspends/resume just fine.
** Patch added: "q.diff"
http
Thanks for picking this up. While disabling all non-dt platforms seems a
bit rude, disabling all "non-multi_v7" defconfig platforms seems to be a
good idea to start with in order to avoid more of such problems.
--
You received this bug notification because you are a member of Kernel
Packages, whi
** 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/1787945
Title:
Tango platform uses __initcall without further checks
Public bug reported:
The TANGO platform is enabled by default in the multiplatform ARM
kernel. However, it calls __initcall in arch/arm/mach-tango/pm.c without
a check whether it actually runs on this hw. This causes an OOPS during
suspend on my Tegra platform. Please disable this (multiplatform
i
It is possible that it didn't show up in older kernels (4.4 for X)
because Tegra didn't used the IOMMU at that time.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linu
It started after upgrade from X to B. This may only show up on Tegra2, which
does not have an IOMMU, and which creates problems if one is registered. Sorry,
I don't understand the technical details. AFAICT, the whole driver is still
broken in mainline kernel (since 3.20). An upstream fixed is cu
** 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/1783746
Title:
ipmmu is always registered
Status in linux package in
Public bug reported:
Hi,
booting the bionic kernel (4.15.0-29-generic) on my Tegra20 device (no
iommu), I found it crashes during display driver setup. The bootlog (and
crash) is attached. Asking on Tegra IRC channel, digetx found that this
is caused by the IPMMU-VMSA driver which is always regis
not all boards require that zImage has the dtb appended. In such a case,
uboot loads the device tree from the a file, preferable in the boot
partition. Loading it from a different partition may require a special
uboot hack.
--
You received this bug notification because you are a member of Kernel
18 matches
Mail list logo
