public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Ahern <dsa@cumulusnetworks.com>
To: Richard Alpe <richard.alpe@ericsson.com>,
	Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>
Cc: "David S. Miller" <davem@davemloft.net>,
	Alexey Kuznetsov <kuznet@ms2.inr.ac.ru>,
	James Morris <jmorris@namei.org>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [linux-next] oops in ip_route_input_noref
Date: Wed, 16 Sep 2015 07:57:30 -0600	[thread overview]
Message-ID: <55F9754A.1030507@cumulusnetworks.com> (raw)
In-Reply-To: <55F97459.5050408@ericsson.com>

On 9/16/15 7:53 AM, Richard Alpe wrote:
>>> I to get an Oops in ip_route_input_noref(). It happens occasionally during bootup.
>>> KVM environment using virtio driver. Let me know if you need any additional info or
>>> if you want me to try to bisect it.
>>>
>>> Starting network...
>>> ...
>>> [    0.877040] BUG: unable to handle kernel NULL pointer dereference at 0000000000000056
>>> [    0.877597] IP: [<ffffffff8155b5e2>] ip_route_input_noref+0x1a2/0xb00
>>
>> Can you send me your kernel config and qemu command line? KVM with virtio networking is a primary test vehicle, and I did not encounter this at all.
> Sure thing. Not sure how ppl normally provide files on netdev but I'm just going
> to go ahead and paste them here :)

An attachment for the config is better than inline.

>
> $ ps aux | grep kvm
> qemu-system-x86_64 -enable-kvm -name tipc-medium-node1 -S -machine pc-0.14,accel=kvm,usb=off -m 1024 -realtime mlock=off -smp 2,sockets=2,cores=1,threads=1 -uuid cdec478a-5f0d-49f1-b25e-fac4ca0b290c -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/tipc-medium-node1.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc -no-shutdown -boot order=n,menu=on,strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -netdev tap,fd=25,id=hostnet0 -device e1000,netdev=hostnet0,id=net0,mac=00:0f:ff:10:04:01,bus=pci.0,addr=0x3 -chardev pty,id=charserial0 -device isa-serial,chardev=charserial0,id=serial0 -vnc 127.0.0.1:28101 -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x4 -msg timestamp=on
>
> $ cat .config
> #
> # Automatically generated file; DO NOT EDIT.
> # Linux/x86 3.12.28 Kernel Configuration
> #

3.12.28? That should say this for net-next:

# Linux/x86 4.2.0 Kernel Configuration

Or are you reporting a problem with 3.12.28?

David

  reply	other threads:[~2015-09-16 13:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-16  9:24 [linux-next] oops in ip_route_input_noref Sergey Senozhatsky
2015-09-16 11:50 ` Richard Alpe
2015-09-16 13:07   ` David Ahern
2015-09-16 13:53     ` Richard Alpe
2015-09-16 13:57       ` David Ahern [this message]
2015-09-16 14:08         ` Richard Alpe
2015-09-16 13:59       ` Richard Alpe
2015-09-16 14:00         ` David Ahern
2015-09-16 23:47     ` Sergey Senozhatsky
2015-09-17  7:26       ` Tomeu Vizoso
2015-09-16 13:24 ` David Ahern
2015-09-16 15:00 ` Fabio Estevam
2015-09-16 15:04   ` David Ahern
2015-09-17  8:58     ` Thierry Reding
2015-09-18 23:06       ` Andrew Morton
2015-09-19 14:34         ` David Ahern

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=55F9754A.1030507@cumulusnetworks.com \
    --to=dsa@cumulusnetworks.com \
    --cc=davem@davemloft.net \
    --cc=jmorris@namei.org \
    --cc=kuznet@ms2.inr.ac.ru \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=richard.alpe@ericsson.com \
    --cc=sergey.senozhatsky.work@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox