[<prev] [next>] [day] [month] [year] [list]
Message-ID: <202211231652.f67208c7-yujie.liu@intel.com>
Date: Wed, 23 Nov 2022 17:25:46 +0800
From: kernel test robot <yujie.liu@...el.com>
To: Sai Prakash Ranjan <quic_saipraka@...cinc.com>
CC: <oe-lkp@...ts.linux.dev>, <lkp@...el.com>,
Arnd Bergmann <arnd@...db.de>,
Linux Memory Management List <linux-mm@...ck.org>,
<linux-arch@...r.kernel.org>, <linux-kernel@...r.kernel.org>
Subject: [linux-next:master] [asm] 5e5ff73c2e: Initramfs_unpacking_failed
Hi Sai,
We encountered an "Initramfs unpacking failed" issue when doing boot
test on this patch. The patch is for printing accurate debug info under
compiler optimization, looks totally unrelated with initramfs, but this
issue is 100% reproducible in our tests. We confirmed that our rootfs
image, kernel config and other environments were consistent during the
testing. Could you please help check if this is a real problem or a
false alarm? Thanks.
Greeting,
FYI, we noticed Initramfs_unpacking_failed due to commit (built with gcc-11):
commit: 5e5ff73c2e5863f93fc5fd78d178cd8f2af12464 ("asm-generic/io: Add _RET_IP_ to MMIO trace for more accurate debug info")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
in testcase: boot
on test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 16G
caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
[ 3.518862][ T1] initcall pci_apply_final_quirks+0x0/0x32c returned 0 after 10472 usecs
[ 3.520299][ T1] calling acpi_reserve_resources+0x0/0x273 @ 1
[ 3.521395][ T1] initcall acpi_reserve_resources+0x0/0x273 returned 0 after 61 usecs
[ 3.522853][ T1] calling populate_rootfs+0x0/0x3c @ 1
[ 3.524393][ T25] Trying to unpack rootfs image as initramfs...
[ 30.185500][ T25] Initramfs unpacking failed: uncompression error <--
[ 30.931793][ T25] Freeing initrd memory: 607016K
[ 30.932869][ T1] initcall populate_rootfs+0x0/0x3c returned 0 after 27409026 usecs
[ 30.934238][ T1] calling pci_iommu_init+0x0/0x55 @ 1
[ 30.935230][ T1] PCI-DMA: Using software bounce buffering for IO (SWIOTLB)
[ 30.936475][ T1] software IO TLB: mapped [mem 0x0000000096f16000-0x000000009af16000] (64MB)
If you fix the issue, kindly add following tag
| Reported-by: kernel test robot <yujie.liu@...el.com>
| Link: https://lore.kernel.org/oe-lkp/202211231652.f67208c7-yujie.liu@intel.com
To reproduce:
# build kernel
cd linux
cp config-6.1.0-rc3-00002-g5e5ff73c2e58.old .config
make HOSTCC=gcc-11 CC=gcc-11 ARCH=x86_64 olddefconfig prepare modules_prepare bzImage modules
make HOSTCC=gcc-11 CC=gcc-11 ARCH=x86_64 INSTALL_MOD_PATH=<mod-install-dir> modules_install
cd <mod-install-dir>
find lib/ | cpio -o -H newc --quiet | gzip > modules.cgz
git clone https://github.com/intel/lkp-tests.git
cd lkp-tests
bin/lkp qemu -k <bzImage> -m modules.cgz job-script # job-script is attached in this email
# if come across any failure that blocks the test,
# please remove ~/.lkp and /lkp dir to run from a clean state.
--
0-DAY CI Kernel Test Service
https://01.org/lkp
Download attachment "config-6.1.0-rc3-00002-g5e5ff73c2e58.old" of type "application/x-trash" (167332 bytes)
View attachment "job-script" of type "text/plain" (4973 bytes)
Download attachment "dmesg.xz" of type "application/x-xz" (28428 bytes)
Powered by blists - more mailing lists