* NULL pointer deref bring up interfaces
@ 2017-08-06 17:29 Rafael Cepeda
2017-08-06 20:54 ` Stephen Hemminger
0 siblings, 1 reply; 2+ messages in thread
From: Rafael Cepeda @ 2017-08-06 17:29 UTC (permalink / raw)
To: netdev
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.
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: NULL pointer deref bring up interfaces
2017-08-06 17:29 NULL pointer deref bring up interfaces Rafael Cepeda
@ 2017-08-06 20:54 ` Stephen Hemminger
0 siblings, 0 replies; 2+ messages in thread
From: Stephen Hemminger @ 2017-08-06 20:54 UTC (permalink / raw)
To: Rafael Cepeda; +Cc: netdev
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.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2017-08-06 20:54 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2017-08-06 17:29 NULL pointer deref bring up interfaces Rafael Cepeda
2017-08-06 20:54 ` Stephen Hemminger
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox