Netdev List
 help / color / mirror / Atom feed
From: "Paweł Staszewski" <pstaszewski@itcare.pl>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Linux Kernel Network Developers <netdev@vger.kernel.org>
Subject: Re: latest netdev net-next kernel panic
Date: Thu, 7 Sep 2017 23:47:08 +0200	[thread overview]
Message-ID: <2e7d813e-0ee9-ede6-7e0e-db2814b3cf94@itcare.pl> (raw)
In-Reply-To: <1504820388.15310.71.camel@edumazet-glaptop3.roam.corp.google.com>

Hi Eric


today upgraded some host from 4.13.0-rc7+ to latest net-next from git

and run some tests simulate clients traffic 40Gbit / 5Mpps mixed tcp + udp

There is also bgpd running that feeds FIB with full bgp feed - about 
700k prefixes (so routing tables is about 700k routes with about 300 
nexthops)


There is also simulated about 1000 ip neigh hosts (arp) with about 300 
ip interfaces assigned on vlans



With kernel 4.13.0-rc7+ (git from 05.09.2017) all tests are good 
(besides that there is panic after about 10 hours - every time same like 
in this link:

https://bugzilla.kernel.org/attachment.cgi?id=258257

But looks like acpi related or c/p states with new intel cpus... dono now.




W dniu 2017-09-07 o 23:39, Eric Dumazet pisze:
> On Thu, 2017-09-07 at 23:30 +0200, Paweł Staszewski wrote:
>> I want to mention also here cause last trace for RIP was dst_dev_put
>>
>> https://bugzilla.kernel.org/attachment.cgi?id=258259
> Can you provide a bit more context ?
>
> Thanks !
>
>
>

  reply	other threads:[~2017-09-07 21:49 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-07 21:30 latest netdev net-next kernel panic Paweł Staszewski
2017-09-07 21:39 ` Eric Dumazet
2017-09-07 21:47   ` Paweł Staszewski [this message]
2017-09-07 22:08     ` Paweł Staszewski
2017-09-07 22:38       ` Paweł Staszewski

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=2e7d813e-0ee9-ede6-7e0e-db2814b3cf94@itcare.pl \
    --to=pstaszewski@itcare.pl \
    --cc=eric.dumazet@gmail.com \
    --cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox