All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Amol Grover <frextrite@gmail.com>
Cc: linux-kernel-mentees@lists.linuxfoundation.org, stable@vger.kernel.org
Subject: Re: [Linux-kernel-mentees] [STABLE TEST] 5.3.13
Date: Tue, 3 Dec 2019 13:03:04 +0100	[thread overview]
Message-ID: <20191203120304.GA2126088@kroah.com> (raw)
In-Reply-To: <20191203071415.GA9640@workstation-portable>

On Tue, Dec 03, 2019 at 12:44:15PM +0530, Amol Grover wrote:
> On Tue, Dec 03, 2019 at 07:40:52AM +0100, Greg KH wrote:
> > On Tue, Dec 03, 2019 at 11:55:03AM +0530, Amol Grover wrote:
> > > Compiled, Booted, however I'm getting the following errors when running
> > > "make kselftest"
> > > 
> > > sudo dmesg -l alert
> > > 
> > > [34381.903893] BUG: kernel NULL pointer dereference, address: 0000000000000008
> > > [34381.903904] #PF: supervisor read access in kernel mode
> > > [34381.903908] #PF: error_code(0x0000) - not-present page
> > 
> > Which test causes this problem?
> 
> IIRC I didn't run make kselftest with summary=1 option. Is there any
> other way to get that information? The logs that kselftest generated
> also don't seem to help in this.

Watch the output when you run this?  I don't know, try re-running it
with that option.

> > ANd is it new in 5.3.13?
> > 
> 
> I previously ran kselftest on 5.4-rc7 and 5.3.9 (default kernel shipped
> by openSUSE), both were fine. However, a bit of backstory:
> 
> A day ago I used kselftest from the linux/next branch and ran it (w/o
> sudo).  It showed me the exact same error. However, I was running a
> modified version of 5.3.13, but those modifications were actually
> trivial (5 lines changed) and shouldn't have resulted in this kernel
> error. So, I switched to the vanilla 5.3.13 and ran kselftest (w/o sudo)
> again. I ran it 3 times (w/o any errors), switched back to the modified
> kernel and ran kselftest (w/o root) 2 more times and everything was
> fine. Then I decided to test the vanilla one again for the 4th time, but
> this time I ran kselftest as root where this BUG popped again.

Try a kernel.org 5.3.9 and if that works, then try 5.3.13 and if that
fails, run 'git bisect' and try to find the offending kernel commit.

thanks,

greg k-h
_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees

WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Amol Grover <frextrite@gmail.com>
Cc: stable@vger.kernel.org, linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [STABLE TEST] 5.3.13
Date: Tue, 3 Dec 2019 13:03:04 +0100	[thread overview]
Message-ID: <20191203120304.GA2126088@kroah.com> (raw)
In-Reply-To: <20191203071415.GA9640@workstation-portable>

On Tue, Dec 03, 2019 at 12:44:15PM +0530, Amol Grover wrote:
> On Tue, Dec 03, 2019 at 07:40:52AM +0100, Greg KH wrote:
> > On Tue, Dec 03, 2019 at 11:55:03AM +0530, Amol Grover wrote:
> > > Compiled, Booted, however I'm getting the following errors when running
> > > "make kselftest"
> > > 
> > > sudo dmesg -l alert
> > > 
> > > [34381.903893] BUG: kernel NULL pointer dereference, address: 0000000000000008
> > > [34381.903904] #PF: supervisor read access in kernel mode
> > > [34381.903908] #PF: error_code(0x0000) - not-present page
> > 
> > Which test causes this problem?
> 
> IIRC I didn't run make kselftest with summary=1 option. Is there any
> other way to get that information? The logs that kselftest generated
> also don't seem to help in this.

Watch the output when you run this?  I don't know, try re-running it
with that option.

> > ANd is it new in 5.3.13?
> > 
> 
> I previously ran kselftest on 5.4-rc7 and 5.3.9 (default kernel shipped
> by openSUSE), both were fine. However, a bit of backstory:
> 
> A day ago I used kselftest from the linux/next branch and ran it (w/o
> sudo).  It showed me the exact same error. However, I was running a
> modified version of 5.3.13, but those modifications were actually
> trivial (5 lines changed) and shouldn't have resulted in this kernel
> error. So, I switched to the vanilla 5.3.13 and ran kselftest (w/o sudo)
> again. I ran it 3 times (w/o any errors), switched back to the modified
> kernel and ran kselftest (w/o root) 2 more times and everything was
> fine. Then I decided to test the vanilla one again for the 4th time, but
> this time I ran kselftest as root where this BUG popped again.

Try a kernel.org 5.3.9 and if that works, then try 5.3.13 and if that
fails, run 'git bisect' and try to find the offending kernel commit.

thanks,

greg k-h

  reply	other threads:[~2019-12-03 12:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-03  6:25 [Linux-kernel-mentees] [STABLE TEST] 5.3.13 Amol Grover
2019-12-03  6:25 ` Amol Grover
2019-12-03  6:40 ` [Linux-kernel-mentees] " Greg KH
2019-12-03  6:40   ` Greg KH
2019-12-03  7:14   ` [Linux-kernel-mentees] " Amol Grover
2019-12-03  7:14     ` Amol Grover
2019-12-03 12:03     ` Greg KH [this message]
2019-12-03 12:03       ` Greg KH
2019-12-03 17:18       ` [Linux-kernel-mentees] " Amol Grover
2019-12-03 17:18         ` Amol Grover

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=20191203120304.GA2126088@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=frextrite@gmail.com \
    --cc=linux-kernel-mentees@lists.linuxfoundation.org \
    --cc=stable@vger.kernel.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.