All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Li <philip.li@intel.com>
To: lkp@lists.01.org
Subject: Re: [net, neigh] 7482e3841d: BUG:unable_to_handle_page_fault_for_address
Date: Thu, 18 Nov 2021 21:01:33 +0800	[thread overview]
Message-ID: <YZZOrSiAyC9dfuSl@rli9-dbox> (raw)
In-Reply-To: <f4ae9b1a-c357-0da7-6c1e-71701c408c61@iogearbox.net>

[-- Attachment #1: Type: text/plain, Size: 2596 bytes --]

On Thu, Nov 18, 2021 at 09:47:51AM +0100, Daniel Borkmann wrote:
> Hi Oliver,
> 
> On 11/18/21 7:23 AM, Oliver Sang wrote:
> > On Fri, Nov 05, 2021 at 12:21:20PM +0100, Daniel Borkmann wrote:
> > > Hey Oliver,
> > > 
> > > > > To reproduce:
> > > > > 
> > > > >           # build kernel
> > > > >      cd linux
> > > > >      cp config-5.15.0-rc4-01167-g7482e3841d52 .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
> > > > > 
> > > > >           # if come across any failure that blocks the test,
> > > > >           # please remove ~/.lkp and /lkp dir to run from a clean state.
> > > 
> > > I ran the test multiple times, but it seems I cannot reproduce. Would be good if you could
> > > double check below whether it looks / passes as expected or if I'm doing something wrong:
> > 
> > sorry about this, we tried above reproducer locally but failed to reproduce
> > either. we are under investigation of this issue.
> 
> Ok, thanks for looking into it!
> 
> > at the same time, we double confirmed by queuing more jobs to our auto-test
> > framework, it still reproduced in a persistent way. Just FYI
> > 2c611ad97a82b512 7482e3841d520a368426ac19672
> > ---------------- ---------------------------
> >         fail:runs  %reproduction    fail:runs
> >             |             |             |
> >             :59          98%          58:58    dmesg.BUG:unable_to_handle_page_fault_for_address
> >             :59          98%          58:58    dmesg.Kernel_panic-not_syncing:Fatal_exception_in_interrupt
> >             :59          98%          58:58    dmesg.Oops:#[##]
> > 
> 
> Is there any way for lkp to test development branches for getting more debug info out of it?
> Something like syzkaller has with 'syz test' where it mails the results back [0]?
thanks for the suggestion, Daniel. So far, we don't support this yet, but this is
very helpful to provide something similar to syzkaller does. We will consider this
seriously as TODO.

> 
> Thanks a lot,
> Daniel
> 
>   [0] https://github.com/google/syzkaller/blob/master/docs/syzbot.md#testing-patches
> _______________________________________________
> LKP mailing list -- lkp(a)lists.01.org
> To unsubscribe send an email to lkp-leave(a)lists.01.org

  reply	other threads:[~2021-11-18 13:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-04 15:21 [net, neigh] 7482e3841d: BUG:unable_to_handle_page_fault_for_address kernel test robot
2021-11-04 15:35 ` Daniel Borkmann
2021-11-05 11:21   ` Daniel Borkmann
2021-11-18  6:23     ` Oliver Sang
2021-11-18  8:47       ` Daniel Borkmann
2021-11-18 13:01         ` Philip Li [this message]
2021-11-18 13:03           ` Daniel Borkmann
2021-11-22  8:52       ` Li Zhijian
2021-11-22 15:04         ` Daniel Borkmann

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=YZZOrSiAyC9dfuSl@rli9-dbox \
    --to=philip.li@intel.com \
    --cc=lkp@lists.01.org \
    /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.