FYI, we noticed the following commit (built with gcc-7):
commit: 9290ec3cea1dd9d312d1230825a75c798b670ea1 ("[PATCH v5 01/48] Input: introduce input_mt_report_slot_inactive")
base: https://git.kernel.org/cgit/linux/kernel/git/xen/tip.git linux-next
in testcase: suspend_stress
with following parameters:
on test machine: 8 threads KabyLake-r with 8G memory
caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
If you fix the issue, kindly add following tag
Reported-by: kernel test robot <rong.a.chen(a)intel.com>
(then just like hang)
(below is what looks like if test can pass
SUSPEND RESUME TEST STARTED
Suspend to freeze 1/10:
Sleep for 10 seconds
Suspend to freeze 2/10:
Suspend to freeze 10/10:
Sleep for 10 seconds
SUSPEND RESUME TEST SUCCESS)
git clone https://github.com/intel/lkp-tests.git
bin/lkp install job.yaml # job file is attached in this email
bin/lkp run job.yaml
On Tue, Nov 12, 2019 at 02:05:27PM +0800, Alex Shi wrote:
> hi Oliver,
> Did you find this error happens on other situations?
Hi Alex, sorry for late. for commit dab70bdf66 we double confirmed the issue
is reproducable in our system (with default gcc 7).
However, when we want to do more manual check, we found your repo was rebased,
right? there is no dab70bdf66 any longer, and we found a similar commit
63c496b29f, but not sure whether it's meaningful to test upon it. have you
rewritten the patch and do you have a commit want us to check? Thanks
> 在 2019/11/11 下午7:38, Alex Shi 写道:
> > Hi Oliver,
> > Thanks for report!
> > I have no gcc-7 version. so I tried the gcc 6.5 with your attached config and there is nothing failed except no rootfs for my image.
> > Did you try the gcc 6 or other version for this issue?
> > And there is another boot failure on 80e0cd52a0? Is there are a bug on that?
> > Thanks!
> > Alex
> > 在 2019/11/5 下午2:50, kernel test robot 写道:
> >> FYI, we noticed the following commit (built with gcc-7):
> >> commit: dab70bdf6650e91a5ec88e1ade261c708620f4d0 ("mm/lru: only change the lru_lock iff page's lruvec is different")
> >> https://github.com/alexshi/linux.git lru_lock
> >> in testcase: boot
> >> on test machine: qemu-system-x86_64 -enable-kvm -cpu SandyBridge -smp 2 -m 8G
>>> [ 1.278970] Trying to unpack rootfs image as initramfs...
>>> [ 4.011404] Initramfs unpacking failed: broken padding
>> Was this test failure unrelated to commit 9393c8de62?
> Seems to be unrelated - a m68k kernel with that commit included, SCSI
> core included but low-level driver built as a module(*) boots into
> the initramfs just fine.
> (*) well-known emulator bug.
I'm scratching my head too. I have tested a variety of systems and all
of them boot and work fine.
Martin K. Petersen Oracle Linux Engineering