All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Rafael Cepeda <rcepeda1993@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: NULL pointer deref bring up interfaces
Date: Sun, 6 Aug 2017 13:54:37 -0700	[thread overview]
Message-ID: <20170806135437.23330bbf@xeon-e3> (raw)
In-Reply-To: <CAEMnpcuw8Ow37_amPQtm66EkLwEpTDHWQFoe5UmFXzczYeQ-1w@mail.gmail.com>

On Sun, 6 Aug 2017 12:29:13 -0500
Rafael Cepeda <rcepeda1993@gmail.com> wrote:

> Just upgraded to 4.13rc2, rebooted, and my system crashed at my
> netmount init script; says RIP is NULL, I am guessing a bad func call.
> I immediately thought missing firmware in kernel, my kernel builds
> firmware in it, so I upgraded my firmware to latest on git.kernel and
> made sure I had no warnings in dmesg about missing firmware. Still, I
> receive this NULL pointer in the IP. If I disable my netmount on boot,
> I can login, but can not bring up my interfaces, still get a RIP err
> in kernel logs and cpu load sky-rockets...the issue still exists on
> rc3.
> 
> Linux-Regression-ID: lr#084be9
> 
> I am willing to help and provide as much info as possible, thank you.

You need to post:
 1. Kernel config -- since you are building your own kernel.
 2. Hardware -- lspci output
 3. Kernel log if possible (use serial console).

Ideally, you can bisect it down to the commit that causes the problem.

      reply	other threads:[~2017-08-06 20:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-06 17:29 NULL pointer deref bring up interfaces Rafael Cepeda
2017-08-06 20:54 ` Stephen Hemminger [this message]

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=20170806135437.23330bbf@xeon-e3 \
    --to=stephen@networkplumber.org \
    --cc=netdev@vger.kernel.org \
    --cc=rcepeda1993@gmail.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.