[Kernel-packages] [Bug 2037214] Re: evict_inodes inode xxx, i_count = 1, was skipped!
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 skipped!
Status in linux package in Ubuntu:
Confirmed
Status in linux-meta-hwe-6.5 package in Ubuntu:
Confirmed
Status in linux-oem-6.5 package in Ubuntu:
Confirmed
Bug description:
Hi,
during boot the kernel logs the following messages:
# dmesg | grep evict_inodes
[ 12.784805] evict_inodes inode d69da69b, i_count = 1, was skipped!
[ 12.784810] evict_inodes inode 8b9a7c55, i_count = 1, was skipped!
[ 12.784811] evict_inodes inode 8ff8e64c, i_count = 1, was skipped!
[ 12.784811] evict_inodes inode 194d080e, i_count = 1, was skipped!
[ 12.784812] evict_inodes inode 09b77b7b, i_count = 1, was skipped!
[ 12.811217] evict_inodes inode ec873c71, i_count = 1, was skipped!
[ 12.811222] evict_inodes inode 72bf501d, i_count = 1, was skipped!
[ 12.811223] evict_inodes inode b42b829a, i_count = 1, was skipped!
[ 12.811224] evict_inodes inode c7c5b4ef, i_count = 1, was skipped!
[ 13.412667] evict_inodes inode 61a23a39, i_count = 1, was skipped!
[ 13.412671] evict_inodes inode b42b829a, i_count = 1, was skipped!
[ 13.412671] evict_inodes inode 72bf501d, i_count = 1, was skipped!
[ 13.412672] evict_inodes inode c7c5b4ef, i_count = 1, was skipped!
[ 13.412673] evict_inodes inode ec873c71, i_count = 1, was skipped!
Those messages are not displayed when I boot my system with a mainline Linux
kernel.
Moreover, in the mainline Linux source code, I do not find the lines where
such a message could be printed.
Therefore, those messages are probably caused by an Ubuntu patch.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-5-generic 6.5.0-5.5
ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0
Uname: Linux 6.5.0-5-generic x86_64
ApportVersion: 2.27.0-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: bonnaudl 4827 F wireplumber
/dev/snd/seq:bonnaudl 4808 F pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Sun Sep 24 14:39:10 2023
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.5.0-5-generic
root=/dev/mapper/MonVolume2-UbuntuRacine ro vsyscall=none security=apparmor
tpm_tis.interrupts=0 preempt=full split_lock_detect=off quiet splash
vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-5-generic N/A
linux-backports-modules-6.5.0-5-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/26/2022
dmi.bios.release: 7.16
dmi.bios.vendor: INSYDE Corp.
dmi.bios.version: 1.07.16NRTR4
dmi.board.asset.tag: Tag 12345
dmi.board.name: NS50_70MU
dmi.board.vendor: TUXEDO
dmi.board.version: Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.ec.firmware.release: 7.7
dmi.modalias:
dmi:bvnINSYDECorp.:bvr1.07.16NRTR4:bd05/26/2022:br7.16:efr7.7:svnTUXEDO:pnTUXEDOInfinityBookS15Gen6:pvrNotApplicable:rvnTUXEDO:rnNS50_70MU:rvrApplicable:cvnNotebook:ct10:cvrN/A:skuNotApplicable:
dmi.product.family: Not Applicable
dmi.product.name: TUXEDO InfinityBook S 15 Gen6
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: TUXEDO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037214/+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 2038837] Re: kernel: evict_inodes inode 000000006048f67c, i_count = 1, was skipped!
*** 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 subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/2038837
Title:
kernel: evict_inodes inode 6048f67c, i_count = 1, was skipped!
Status in linux package in Ubuntu:
Confirmed
Bug description:
This gets spammed after I shutdown, though the inode values are
different for each line. Had to phyically reboot to get it to reboot.
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: linux-image-6.5.0-9-generic 6.5.0-9.9
ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3
Uname: Linux 6.5.0-9-generic x86_64
ApportVersion: 2.27.0-0ubuntu4
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC2: yamiyuki 6735 F wireplumber
/dev/snd/controlC0: yamiyuki 6735 F wireplumber
/dev/snd/controlC1: yamiyuki 6735 F wireplumber
/dev/snd/seq:yamiyuki 6731 F pipewire
CRDA: N/A
CasperMD5CheckResult: pass
CurrentDesktop: KDE
Date: Mon Oct 9 11:32:47 2023
InstallationDate: Installed on 2022-01-14 (634 days ago)
InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: root=UUID=1f611ee1-b4c4-4178-8681-c1e1fe158f52 ro
rootflags=subvol=@ amd_iommu=on iommu=pt kvm_amd.npt=1 kvm_amd.avic=1
vfio-pci.ids=10de:2486,10de:228b,1b21:2142 amdgpu.ppfeaturemask=0x
quiet splash vt.handoff=7 initrd=@\boot\initrd.img-6.5.0-9-generic
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
linux-restricted-modules-6.5.0-9-generic N/A
linux-backports-modules-6.5.0-9-generic N/A
linux-firmware 20230919.git3672ccab-0ubuntu2
SourcePackage: linux
UpgradeStatus: Upgraded to mantic on 2023-09-30 (9 days ago)
dmi.bios.date: 02/08/2023
dmi.bios.release: 5.17
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: F5a
dmi.board.asset.tag: Default string
dmi.board.name: X570S AORUS MASTER
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: Default string
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias:
dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF5a:bd02/08/2023:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570SAORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570SAORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: X570 MB
dmi.product.name: X570S AORUS MASTER
dmi.product.sku: Default string
dmi.product.version: -CF
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
modified.conffile..etc.default.apport:
# set this to 0 to disable apport, or to 1 to enable it
# you can temporarily override this with
# sudo service apport start force_start=1
enabled=0
mtime.conffile..etc.default.apport: 2023-02-05T17:07:36.420620
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2038837/+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 1783746] Re: ipmmu is always registered
** 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 linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Bug description: [Impact] The ipmmu-vmsa driver registers itself to the system via an initcall() to ipmmu_init(), and in case it's the first (or the only) iommu driver, it registers its iommu ops to the platform bus - in the tegra2 case, there's no iommu hardware, so all drivers bail out, except for the ipmmu-vmsa. Later on, during boot, when the Tegra host1x is probing (drivers/gpu/host1x/dev.c::host1x_probe()), it checks if an iommu device is present (drivers/iommu/iommu.c::iommu_present() that does so by identifying if any iommu ops were registered) and attach to the supposedly present device, incurring in a null pointer dereference. Upstream quickly acknowledged the problem, and rolled a patch to restrict the ipmmu-vmsa driver to register if and only if a compatible device is present. The fix appared initially in 4.19, and was later backported via stable to 4.18.x, and this is a clean cherry pick of that commit. [Fix] Apply the attached patch and recompile. [How to test] Try to boot a patched kernel on a Tegra2 board. [Regession potential] None, the fix is trivial. -- Original bug: 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 registered via initcall. Adding "initcall_blacklist=ipmmu_init" to the kernel parameters makes it boot fine. Maybe this buggy driver should be disabled in the config (or fixed somehow)? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783746/+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 1787945] Re: Tango platform uses __initcall without further checks
** 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 further checks Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: Impact: The TANGO platform (an embedded soc used in home entertainment, connectivity and control devices) is enabled by default in the generic arm kernel. During kernel bootup, the tango platform blindly registers its pm ops in arch/arm/mach-tango/pm.c via initcalls() (without checking whether it's actually running on the correspondent hardware) and this causes OOPS during suspend on tegra platforms since the tango pm .enter function directly pokes the underlying hardware. Given the narrow scope of this SOC, i propose to disable support for the TANGO arch. Fix: Apply the attached patch and recompile. How to test: Suspend the tegra board and chek that it worked - either close the laptop lid, 'systemctl suspend' or: # echo -n mem > /sys/power/state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787945/+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 1787945] Re: Tango platform uses __initcall without further checks
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" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787945/+attachment/5179894/+files/q.diff -- 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 Status in linux package in Ubuntu: Confirmed Bug description: Impact: The TANGO platform (an embedded soc used in home entertainment, connectivity and control devices) is enabled by default in the generic arm kernel. During kernel bootup, the tango platform blindly registers its pm ops in arch/arm/mach-tango/pm.c via initcalls() (without checking whether it's actually running on the correspondent hardware) and this causes OOPS during suspend on tegra platforms since the tango pm .enter function directly pokes the underlying hardware. Given the narrow scope of this SOC, i propose to disable support for the TANGO arch. Fix: Apply the attached patch and recompile. How to test: Suspend the tegra board and chek that it worked - either close the laptop lid, 'systemctl suspend' or: # echo -n mem > /sys/power/state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787945/+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 1787945] Re: Tango platform uses __initcall without further checks
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, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1787945 Title: Tango platform uses __initcall without further checks Status in linux package in Ubuntu: Confirmed Bug description: 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 incompatible) arch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787945/+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 1787945] Re: Tango platform uses __initcall without further checks
** 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 Status in linux package in Ubuntu: Confirmed Bug description: 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 incompatible) arch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787945/+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 1787945] [NEW] 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 incompatible) arch. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: 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 further checks Status in linux package in Ubuntu: New Bug description: 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 incompatible) arch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1787945/+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 1783746] Re: ipmmu is always registered
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 linux in Ubuntu. https://bugs.launchpad.net/bugs/1783746 Title: ipmmu is always registered Status in linux package in Ubuntu: Confirmed Bug description: 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 registered via initcall. Adding "initcall_blacklist=ipmmu_init" to the kernel parameters makes it boot fine. Maybe this buggy driver should be disabled in the config (or fixed somehow)? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783746/+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 1783746] Re: ipmmu is always registered
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 currently proposed. See: https://git.kernel.org/pub/scm/linux/kernel/git/joro/iommu.git/commit/?h=next&id=5c5c87411488af3cd082221e567498d813d0fe83 -- 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 Ubuntu: Incomplete Bug description: 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 registered via initcall. Adding "initcall_blacklist=ipmmu_init" to the kernel parameters makes it boot fine. Maybe this buggy driver should be disabled in the config (or fixed somehow)? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783746/+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 1783746] Re: ipmmu is always registered
** 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 Ubuntu: Confirmed Bug description: 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 registered via initcall. Adding "initcall_blacklist=ipmmu_init" to the kernel parameters makes it boot fine. Maybe this buggy driver should be disabled in the config (or fixed somehow)? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783746/+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 1783746] [NEW] ipmmu is always registered
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 registered via initcall. Adding "initcall_blacklist=ipmmu_init" to the kernel parameters makes it boot fine. Maybe this buggy driver should be disabled in the config (or fixed somehow)? ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: bionic ** Attachment added: "bootlog" https://bugs.launchpad.net/bugs/1783746/+attachment/5168044/+files/paste_1035175 -- 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 Ubuntu: Incomplete Bug description: 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 registered via initcall. Adding "initcall_blacklist=ipmmu_init" to the kernel parameters makes it boot fine. Maybe this buggy driver should be disabled in the config (or fixed somehow)? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783746/+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 1364035] Re: armhf: dtb movement from /lib/firmware/$(uname -r) to /boot/$(uname -r)
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 Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1364035 Title: armhf: dtb movement from /lib/firmware/$(uname -r) to /boot/$(uname -r) Status in kernel-wedge package in Ubuntu: In Progress Status in linux package in Ubuntu: Triaged Status in linux-meta package in Ubuntu: New Status in linux-raspi2 package in Ubuntu: New Status in kernel-wedge source package in Utopic: In Progress Status in linux source package in Utopic: Triaged Status in linux-hammerhead source package in Utopic: New Status in linux-meta source package in Utopic: New Status in linux-raspi2 source package in Utopic: New Bug description: This is a placeholder to coordinate all the efforts required to move the DTB files from the previous location /lib/firmware/$(uname -r) to /boot/$(uname -r) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kernel-wedge/+bug/1364035/+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
