From: Yujie Liu <yujie.liu@intel.com>
To: Liam Howlett <liam.howlett@oracle.com>
Cc: Davidlohr Bueso <dave@stgolabs.net>,
David Hildenbrand <david@redhat.com>,
Catalin Marinas <catalin.marinas@arm.com>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Matthew Wilcox <willy@infradead.org>,
David Howells <dhowells@redhat.com>,
"lkp@lists.01.org" <lkp@lists.01.org>,
SeongJae Park <sj@kernel.org>,
kernel test robot <oliver.sang@intel.com>,
Sven Schnelle <svens@linux.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Will Deacon <will@kernel.org>, Vlastimil Babka <vbabka@suse.cz>,
Yu Zhao <yuzhao@google.com>
Subject: Re: [Intel-gfx] [linus:master] [i915] f683b9d613: igt.gem_userptr_blits.probe.fail
Date: Wed, 26 Oct 2022 16:17:01 +0800 [thread overview]
Message-ID: <Y1js/ZTP+e0UEdWD@yujie-X299> (raw)
In-Reply-To: <20221024150734.zjo46njdblmykczj@revolver>
Hi Liam,
On Mon, Oct 24, 2022 at 03:07:54PM +0000, Liam Howlett wrote:
> * kernel test robot <oliver.sang@intel.com> [221024 01:06]:
> >
> > Greeting,
> >
> > FYI, we noticed igt.gem_userptr_blits.probe.fail due to commit (built with gcc-11):
> >
> > commit: f683b9d613193362ceb954c216f663a43c027302 ("i915: use the VMA iterator")
> > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
> >
> > in testcase: igt
> > version: igt-x86_64-cf55acde-1_20221012
> > with following parameters:
> >
> > group: group-13
> >
> >
> >
> > on test machine: 20 threads 1 sockets (Commet Lake) with 16G 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 <oliver.sang@intel.com>
> > | Link: https://lore.kernel.org/r/202210241246.68be2f11-oliver.sang@intel.com
> >
> >
> >
> > 2022-10-24 03:27:39 build/tests/gem_userptr_blits --run-subtest probe
> > IGT-Version: 1.26-gcf55acde (x86_64) (Linux: 6.0.0-rc3-00280-gf683b9d61319 x86_64)
> > Aperture size is 268435456 MiB
> > Total RAM is 13505 MiB
> > Not enough RAM to run test, reducing buffer count.
> > Test requirement not met in function __igt_unique____real_main2320, file ../tests/i915/gem_userptr_blits.c:2401:
> > Test requirement: has_userptr(fd)
> > Starting subtest: probe
> > (gem_userptr_blits:1984) CRITICAL: Test assertion failure function test_probe, file ../tests/i915/gem_userptr_blits.c:2231:
> > (gem_userptr_blits:1984) CRITICAL: Failed assertion: __gem_userptr(fd, ptr + 4096, 3*4096, 0, 0x2, &handle) == expected
> > (gem_userptr_blits:1984) CRITICAL: Last errno: 14, Bad address
> > (gem_userptr_blits:1984) CRITICAL: error: 0 != -14
> > Subtest probe failed.
> > **** DEBUG ****
> > (gem_userptr_blits:1984) DEBUG: Test requirement passed: has_userptr_probe(fd)
> > (gem_userptr_blits:1984) CRITICAL: Test assertion failure function test_probe, file ../tests/i915/gem_userptr_blits.c:2231:
> > (gem_userptr_blits:1984) CRITICAL: Failed assertion: __gem_userptr(fd, ptr + 4096, 3*4096, 0, 0x2, &handle) == expected
> > (gem_userptr_blits:1984) CRITICAL: Last errno: 14, Bad address
> > (gem_userptr_blits:1984) CRITICAL: error: 0 != -14
> > (gem_userptr_blits:1984) igt_core-INFO: Stack trace:
> > (gem_userptr_blits:1984) igt_core-INFO: #0 [__igt_fail_assert+0x106]
> > (gem_userptr_blits:1984) igt_core-INFO: #1 ../tests/i915/gem_userptr_blits.c:801 __igt_unique____real_main2320()
> > (gem_userptr_blits:1984) igt_core-INFO: #2 ../tests/i915/gem_userptr_blits.c:2320 main()
> > (gem_userptr_blits:1984) igt_core-INFO: #3 ../csu/libc-start.c:308 __libc_start_main()
> > (gem_userptr_blits:1984) igt_core-INFO: #4 [_start+0x2a]
> > **** END ****
> > Stack trace:
> > #0 [__igt_fail_assert+0x106]
> > #1 ../tests/i915/gem_userptr_blits.c:801 __igt_unique____real_main2320()
> > #2 ../tests/i915/gem_userptr_blits.c:2320 main()
> > #3 ../csu/libc-start.c:308 __libc_start_main()
> > #4 [_start+0x2a]
> > Subtest probe: FAIL (0.052s)
> >
> >
> >
> > To reproduce:
> >
> > git clone https://github.com/intel/lkp-tests.git
> > cd lkp-tests
> > sudo bin/lkp install job.yaml # job file is attached in this email
> > bin/lkp split-job --compatible job.yaml # generate the yaml file for lkp run
> > sudo bin/lkp run generated-yaml-file
> >
> > # if come across any failure that blocks the test,
> > # please remove ~/.lkp and /lkp dir to run from a clean state.
> >
>
> These steps seem insufficient. Initially, it failed complaining about a
> missing config so I created the directory manually and copied the
> confing in only to have it fail again:
>
> lkp-tests/filters/need_kconfig_hw.rb:11:in `load_kernel_context':
> context.yaml doesn't exist:
> /pkg/linux/x86_64-rhel-8.3-func/gcc-11/f683b9d613193362ceb954c216f663a43c027302/context.yaml
>
> Is there a full set of instructions for recreation?
Sorry for the unclear reproducing steps. Seems it is due to bug in our
split-job code, we will fix it soon. Could you please try below steps
instead to see if the problem can be reproduced? Thanks.
# Build kernel on commit f683b9d61319 with the attached config in
# original report, and boot it on a machine.
$ git clone https://github.com/intel/lkp-tests.git
$ cd lkp-tests
$ bin/lkp split-job --compatible jobs/igt-part2.yaml
jobs/igt-part2.yaml => ./igt-part2-group-10.yaml
jobs/igt-part2.yaml => ./igt-part2-group-11.yaml
jobs/igt-part2.yaml => ./igt-part2-group-12.yaml
jobs/igt-part2.yaml => ./igt-part2-group-13.yaml
jobs/igt-part2.yaml => ./igt-part2-group-14.yaml
jobs/igt-part2.yaml => ./igt-part2-group-15.yaml
jobs/igt-part2.yaml => ./igt-part2-group-16.yaml
jobs/igt-part2.yaml => ./igt-part2-group-17.yaml
jobs/igt-part2.yaml => ./igt-part2-group-18.yaml
jobs/igt-part2.yaml => ./igt-part2-group-19.yaml
$ sudo bin/lkp install igt-part2-group-13.yaml
$ sudo bin/lkp run igt-part2-group-13.yaml
--
Best Regards,
Yujie
WARNING: multiple messages have this Message-ID (diff)
From: Yujie Liu <yujie.liu@intel.com>
To: Liam Howlett <liam.howlett@oracle.com>
Cc: kernel test robot <oliver.sang@intel.com>,
Matthew Wilcox <willy@infradead.org>,
"lkp@lists.01.org" <lkp@lists.01.org>,
"lkp@intel.com" <lkp@intel.com>,
Andrew Morton <akpm@linux-foundation.org>,
Vlastimil Babka <vbabka@suse.cz>, Yu Zhao <yuzhao@google.com>,
Catalin Marinas <catalin.marinas@arm.com>,
David Hildenbrand <david@redhat.com>,
"David Howells" <dhowells@redhat.com>,
Davidlohr Bueso <dave@stgolabs.net>,
"SeongJae Park" <sj@kernel.org>,
Sven Schnelle <svens@linux.ibm.com>,
Will Deacon <will@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"intel-gfx@lists.freedesktop.org"
<intel-gfx@lists.freedesktop.org>
Subject: Re: [linus:master] [i915] f683b9d613: igt.gem_userptr_blits.probe.fail
Date: Wed, 26 Oct 2022 16:17:01 +0800 [thread overview]
Message-ID: <Y1js/ZTP+e0UEdWD@yujie-X299> (raw)
In-Reply-To: <20221024150734.zjo46njdblmykczj@revolver>
Hi Liam,
On Mon, Oct 24, 2022 at 03:07:54PM +0000, Liam Howlett wrote:
> * kernel test robot <oliver.sang@intel.com> [221024 01:06]:
> >
> > Greeting,
> >
> > FYI, we noticed igt.gem_userptr_blits.probe.fail due to commit (built with gcc-11):
> >
> > commit: f683b9d613193362ceb954c216f663a43c027302 ("i915: use the VMA iterator")
> > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
> >
> > in testcase: igt
> > version: igt-x86_64-cf55acde-1_20221012
> > with following parameters:
> >
> > group: group-13
> >
> >
> >
> > on test machine: 20 threads 1 sockets (Commet Lake) with 16G 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 <oliver.sang@intel.com>
> > | Link: https://lore.kernel.org/r/202210241246.68be2f11-oliver.sang@intel.com
> >
> >
> >
> > 2022-10-24 03:27:39 build/tests/gem_userptr_blits --run-subtest probe
> > IGT-Version: 1.26-gcf55acde (x86_64) (Linux: 6.0.0-rc3-00280-gf683b9d61319 x86_64)
> > Aperture size is 268435456 MiB
> > Total RAM is 13505 MiB
> > Not enough RAM to run test, reducing buffer count.
> > Test requirement not met in function __igt_unique____real_main2320, file ../tests/i915/gem_userptr_blits.c:2401:
> > Test requirement: has_userptr(fd)
> > Starting subtest: probe
> > (gem_userptr_blits:1984) CRITICAL: Test assertion failure function test_probe, file ../tests/i915/gem_userptr_blits.c:2231:
> > (gem_userptr_blits:1984) CRITICAL: Failed assertion: __gem_userptr(fd, ptr + 4096, 3*4096, 0, 0x2, &handle) == expected
> > (gem_userptr_blits:1984) CRITICAL: Last errno: 14, Bad address
> > (gem_userptr_blits:1984) CRITICAL: error: 0 != -14
> > Subtest probe failed.
> > **** DEBUG ****
> > (gem_userptr_blits:1984) DEBUG: Test requirement passed: has_userptr_probe(fd)
> > (gem_userptr_blits:1984) CRITICAL: Test assertion failure function test_probe, file ../tests/i915/gem_userptr_blits.c:2231:
> > (gem_userptr_blits:1984) CRITICAL: Failed assertion: __gem_userptr(fd, ptr + 4096, 3*4096, 0, 0x2, &handle) == expected
> > (gem_userptr_blits:1984) CRITICAL: Last errno: 14, Bad address
> > (gem_userptr_blits:1984) CRITICAL: error: 0 != -14
> > (gem_userptr_blits:1984) igt_core-INFO: Stack trace:
> > (gem_userptr_blits:1984) igt_core-INFO: #0 [__igt_fail_assert+0x106]
> > (gem_userptr_blits:1984) igt_core-INFO: #1 ../tests/i915/gem_userptr_blits.c:801 __igt_unique____real_main2320()
> > (gem_userptr_blits:1984) igt_core-INFO: #2 ../tests/i915/gem_userptr_blits.c:2320 main()
> > (gem_userptr_blits:1984) igt_core-INFO: #3 ../csu/libc-start.c:308 __libc_start_main()
> > (gem_userptr_blits:1984) igt_core-INFO: #4 [_start+0x2a]
> > **** END ****
> > Stack trace:
> > #0 [__igt_fail_assert+0x106]
> > #1 ../tests/i915/gem_userptr_blits.c:801 __igt_unique____real_main2320()
> > #2 ../tests/i915/gem_userptr_blits.c:2320 main()
> > #3 ../csu/libc-start.c:308 __libc_start_main()
> > #4 [_start+0x2a]
> > Subtest probe: FAIL (0.052s)
> >
> >
> >
> > To reproduce:
> >
> > git clone https://github.com/intel/lkp-tests.git
> > cd lkp-tests
> > sudo bin/lkp install job.yaml # job file is attached in this email
> > bin/lkp split-job --compatible job.yaml # generate the yaml file for lkp run
> > sudo bin/lkp run generated-yaml-file
> >
> > # if come across any failure that blocks the test,
> > # please remove ~/.lkp and /lkp dir to run from a clean state.
> >
>
> These steps seem insufficient. Initially, it failed complaining about a
> missing config so I created the directory manually and copied the
> confing in only to have it fail again:
>
> lkp-tests/filters/need_kconfig_hw.rb:11:in `load_kernel_context':
> context.yaml doesn't exist:
> /pkg/linux/x86_64-rhel-8.3-func/gcc-11/f683b9d613193362ceb954c216f663a43c027302/context.yaml
>
> Is there a full set of instructions for recreation?
Sorry for the unclear reproducing steps. Seems it is due to bug in our
split-job code, we will fix it soon. Could you please try below steps
instead to see if the problem can be reproduced? Thanks.
# Build kernel on commit f683b9d61319 with the attached config in
# original report, and boot it on a machine.
$ git clone https://github.com/intel/lkp-tests.git
$ cd lkp-tests
$ bin/lkp split-job --compatible jobs/igt-part2.yaml
jobs/igt-part2.yaml => ./igt-part2-group-10.yaml
jobs/igt-part2.yaml => ./igt-part2-group-11.yaml
jobs/igt-part2.yaml => ./igt-part2-group-12.yaml
jobs/igt-part2.yaml => ./igt-part2-group-13.yaml
jobs/igt-part2.yaml => ./igt-part2-group-14.yaml
jobs/igt-part2.yaml => ./igt-part2-group-15.yaml
jobs/igt-part2.yaml => ./igt-part2-group-16.yaml
jobs/igt-part2.yaml => ./igt-part2-group-17.yaml
jobs/igt-part2.yaml => ./igt-part2-group-18.yaml
jobs/igt-part2.yaml => ./igt-part2-group-19.yaml
$ sudo bin/lkp install igt-part2-group-13.yaml
$ sudo bin/lkp run igt-part2-group-13.yaml
--
Best Regards,
Yujie
next prev parent reply other threads:[~2022-10-26 8:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 5:05 [Intel-gfx] [linus:master] [i915] f683b9d613: igt.gem_userptr_blits.probe.fail kernel test robot
2022-10-24 5:05 ` kernel test robot
2022-10-24 15:07 ` [Intel-gfx] " Liam Howlett
2022-10-24 15:07 ` Liam Howlett
2022-10-26 8:17 ` Yujie Liu [this message]
2022-10-26 8:17 ` Yujie Liu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y1js/ZTP+e0UEdWD@yujie-X299 \
--to=yujie.liu@intel.com \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=dave@stgolabs.net \
--cc=david@redhat.com \
--cc=dhowells@redhat.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=liam.howlett@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@lists.01.org \
--cc=oliver.sang@intel.com \
--cc=sj@kernel.org \
--cc=svens@linux.ibm.com \
--cc=vbabka@suse.cz \
--cc=will@kernel.org \
--cc=willy@infradead.org \
--cc=yuzhao@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.