From: Lars Poeschel <poeschel@lemonage.de>
To: "Sang, Oliver" <oliver.sang@intel.com>
Cc: Miguel Ojeda <ojeda@kernel.org>, lkp <lkp@intel.com>,
Willy Tarreau <w@1wt.eu>, LKML <linux-kernel@vger.kernel.org>,
Linux Memory Management List <linux-mm@kvack.org>,
"lkp@lists.01.org" <lkp@lists.01.org>
Subject: Re: [LKP] Re: [auxdisplay] b26deabb1d: BUG:kernel_NULL_pointer_dereference,address
Date: Mon, 16 Nov 2020 11:05:04 +0100 [thread overview]
Message-ID: <20201116100504.tccqktcgxwn4pyqd@lem-wkst-02.lemonage> (raw)
In-Reply-To: <983cc8dc58a24dd1a839e05213fb1ffb@intel.com>
On Thu, Nov 12, 2020 at 01:29:31PM +0000, Sang, Oliver wrote:
>
>
> > -----Original Message-----
> > From: Lars Poeschel <poeschel@lemonage.de>
> > Sent: Monday, November 9, 2020 8:40 PM
> > To: Sang, Oliver <oliver.sang@intel.com>
> > Cc: Miguel Ojeda <ojeda@kernel.org>; lkp <lkp@intel.com>; Willy Tarreau
> > <w@1wt.eu>; LKML <linux-kernel@vger.kernel.org>; Linux Memory
> > Management List <linux-mm@kvack.org>; lkp@lists.01.org
> > Subject: [LKP] Re: [auxdisplay] b26deabb1d:
> > BUG:kernel_NULL_pointer_dereference,address
> >
> > Hi!
> >
> > And thanks for your report.
> >
> > On Mon, Nov 09, 2020 at 02:29:34PM +0800, kernel test robot wrote:
> >
> > > To reproduce:
> > >
> > > # build kernel
> > > cd linux
> > > cp config-5.10.0-rc2-00008-gb26deabb1d91 .config
> > > make HOSTCC=gcc-9 CC=gcc-9 ARCH=i386 olddefconfig prepare
> > > modules_prepare bzImage
> > >
> > > git clone https://github.com/intel/lkp-tests.git
> > > cd lkp-tests
> > > bin/lkp qemu -k <bzImage> job-script # job-script is attached
> > > in this email
> >
> > Trying to reproduce your issue:
> >
> > LANG=C bin/lkp qemu -k ~/projekte/linux-stable/arch/x86_64/boot/bzImage
> > /tmp/job-script
> > result_root: /home/larsi/.lkp//result/trinity/300s/vm-snb-i386/yocto-i386-
> > minimal-20190520.cgz/i386-randconfig-a002-20201105/gcc-
> > 9/b26deabb1d915fe87d395081bbd3058b938dee89/6
> > downloading initrds ...
> > /usr/bin/wget -q --timeout=1800 --tries=1 --local-encoding=UTF-8
> > https://download.01.org/0day-ci/lkp-qemu/osimage/yocto/yocto-i386-
> > minimal-20190520.cgz -N -P /home/larsi/.lkp/cache/osimage/yocto
> > 17916 blocks
> > /usr/bin/wget -q --timeout=1800 --tries=1 --local-encoding=UTF-8
> > https://download.01.org/0day-ci/lkp-qemu/osimage/pkg/yocto-i386-minimal-
> > 20190520.cgz/trinity-i386.cgz -N -P /home/larsi/.lkp/cache/osimage/pkg/yocto-
> > i386-minimal-20190520.cgz
> > Failed to download osimage/pkg/yocto-i386-minimal-20190520.cgz/trinity-
> > i386.cgz
> >
> > It seems, that the trinity-i386.cgz file is not downloadable. Using a webbrowser I
> > can see an empty directory.
> > Can you help please ?
>
> sorry for this. just uploaded. https://download.01.org/0day-ci/lkp-qemu/osimage/pkg/yocto-i386-minimal-20190520.cgz/trinity-i386.cgz
> could you try again?
It is working now and I can reproduce the error.
Thank you!
next prev parent reply other threads:[~2020-11-16 10:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-09 6:29 kernel test robot
2020-11-09 12:40 ` Lars Poeschel
2020-11-12 13:29 ` [LKP] " Sang, Oliver
2020-11-16 10:05 ` Lars Poeschel [this message]
2020-11-16 14:39 ` Sang, Oliver
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=20201116100504.tccqktcgxwn4pyqd@lem-wkst-02.lemonage \
--to=poeschel@lemonage.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=lkp@lists.01.org \
--cc=ojeda@kernel.org \
--cc=oliver.sang@intel.com \
--cc=w@1wt.eu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox